C
Curt
I have to extract data from legacy Access 2.0 databases.
We were running the process on Windows NT4, but now we've
upgraded to Windows 2000. Due to the changes in the MDAC
libraries, I need to convert my Access 2.0 databases to
Access 2002 before I run my automated extract process on
them.
I developed a small VB application to automatically
convert the Access 2.0 database to Access 2002. I
developed the application in VB5 on Windows XP. It works
fine in this environment.
However, our deployment environment is Windows 2000.
When I run my process, it fails. So, I just tried to
double-click on the Access 2.0 file, and I receive a
couple errors from Access 2002:
1.) Cannot find the *.mdb file.
I'd like to post the exact message, but this particular
error is hard to recreate. However, I find this error
message to be odd since I double-clicked on the *.mdb
file, so Windows shouldn't be complaining about not being
able to find it.
2.) Microsoft Access failed to convert or enable your
code modules.
Your computer may be low on disk space or memory.
With this second error, which I always get, sometimes the
database will open anyway or it'll open just fine on the
second attempt.
I have verified that there's ample disk space and memory,
so I think this is another bogus error message.
The automated process uses the call:
Set acObj = CreateObject("Access.Application")
acObj.ConvertAccessProject oldDbPath, newDbPath, 10
It gets part way through the conversion, then dies. The
error log reads:
Error converting database: The Microsoft Jet database
engine could not find the object ''. Make sure the
object exists and that you spell its name and the path
name correctly.
I have tried with other Access 2.0 databases with the
same result.
The ODBC driver version we are using on Windows 2000 is
4.00.6200.00
The version we use on our WinXP development machines is
4.00.6019.00
I have limited control over the tools and dll versions
that are being used. If there is something wrong with
the versions, I can forward up to the SA to see if they
could change them.
If anyone has an idea what the problem may be, I'd
appreciate the suggestion.
Thank you,
Curt
We were running the process on Windows NT4, but now we've
upgraded to Windows 2000. Due to the changes in the MDAC
libraries, I need to convert my Access 2.0 databases to
Access 2002 before I run my automated extract process on
them.
I developed a small VB application to automatically
convert the Access 2.0 database to Access 2002. I
developed the application in VB5 on Windows XP. It works
fine in this environment.
However, our deployment environment is Windows 2000.
When I run my process, it fails. So, I just tried to
double-click on the Access 2.0 file, and I receive a
couple errors from Access 2002:
1.) Cannot find the *.mdb file.
I'd like to post the exact message, but this particular
error is hard to recreate. However, I find this error
message to be odd since I double-clicked on the *.mdb
file, so Windows shouldn't be complaining about not being
able to find it.
2.) Microsoft Access failed to convert or enable your
code modules.
Your computer may be low on disk space or memory.
With this second error, which I always get, sometimes the
database will open anyway or it'll open just fine on the
second attempt.
I have verified that there's ample disk space and memory,
so I think this is another bogus error message.
The automated process uses the call:
Set acObj = CreateObject("Access.Application")
acObj.ConvertAccessProject oldDbPath, newDbPath, 10
It gets part way through the conversion, then dies. The
error log reads:
Error converting database: The Microsoft Jet database
engine could not find the object ''. Make sure the
object exists and that you spell its name and the path
name correctly.
I have tried with other Access 2.0 databases with the
same result.
The ODBC driver version we are using on Windows 2000 is
4.00.6200.00
The version we use on our WinXP development machines is
4.00.6019.00
I have limited control over the tools and dll versions
that are being used. If there is something wrong with
the versions, I can forward up to the SA to see if they
could change them.
If anyone has an idea what the problem may be, I'd
appreciate the suggestion.
Thank you,
Curt