D
dschl
Oh, please help, before I go completely mad . . .
I'm using VB6 and Replication Objects 2.6 to convert an Access 97
database to Access 2003. I'm using the
jro.CompactDatabase(...ms.jet.4.0...) method to perform the conversion.
When opening the converted db in Access03, I get "...object is
read-only" messages and Access fails to open it. If I use the
tools/Utils/Convert to 2003 (with no open databases), Access just quits
trying and no new database is created and no error message published --
even in the XP event logs.
If I try to open the VB-converted database, and select the convert
option from the "open" script, I get a single "read-only" message but
the conversion proceeds to a 2000 format.
What's with the error message? There are no forms, reports, or modules,
just queries, and tables. What's read-only?
During the conversion, I specify "engine type=5" which is the default.
Why doesn't the Jet4x produce 2003 format databases?
This seems terribly broken, to me. What's the trick?
Please help! I'm starting to twitch.
I'm using VB6 and Replication Objects 2.6 to convert an Access 97
database to Access 2003. I'm using the
jro.CompactDatabase(...ms.jet.4.0...) method to perform the conversion.
When opening the converted db in Access03, I get "...object is
read-only" messages and Access fails to open it. If I use the
tools/Utils/Convert to 2003 (with no open databases), Access just quits
trying and no new database is created and no error message published --
even in the XP event logs.
If I try to open the VB-converted database, and select the convert
option from the "open" script, I get a single "read-only" message but
the conversion proceeds to a 2000 format.
What's with the error message? There are no forms, reports, or modules,
just queries, and tables. What's read-only?
During the conversion, I specify "engine type=5" which is the default.
Why doesn't the Jet4x produce 2003 format databases?
This seems terribly broken, to me. What's the trick?
Please help! I'm starting to twitch.