On May 23, 11:26=A0pm, Chris Martin <nr.cmartin.dfgh....@[EMAIL PROTECTED]
>
wrote:
> I encountered the same error trying to ex****t/im****t an MDB as text:
>
> =A0 =A0 Error 2205 (Database Name) can't create the output file.
>
> I was using the same posted code. The error occurred at the same place
as
> Wayne's attempt: =A0app.LoadFromText acForm, Name, FileName
>
> Same error was thrown for re****ts as for forms, however qry defs and
> modules re-loaded without error. Wayne wondered if the error related to
> compatibility between versions (a converted Access 2000 database). Mine
> was a converted Access 2000 database as well, so I did some
experimenting.=
>
> Starting from scratch, I converted the Access 2000 mdb to Access 2003
> using the 'Convert Database' menu tool. The resulting database
> consistently threw error 2205 with this code.
>
> I then created a new (empty) 2003 mdb and im****ted all objects from the
> original mdb. The resulting database was error-free when running the
text
> ex****t/im****t code.
>
> This confirms that the problem likely relates to non-native 2003
databases=
> (converted from Access 2000). Apparently when Access im****ts objects
from
> A2000 into A2003 it creates 'pure' A2003 objects, whereas the 'Convert
> Database' menu tool yields some obscure differences.
>
> FWIW, I have included below (after the quoted text from Wayne) the 2
text
> files from the same (simple) form, (1) ex****ted from the
> A2000-converted-to-A2003, and (2) ex****ted from the native A2003
version.
> There are 2 lines in the native 2003 version which are not in the
> converted version:
Thanks for the reply (and detective work) Chris. I'll im****t all
objects into a new A2003 database and see how it goes.
|
