Access 2003 Conversion problems

[Greg]

We are upgrading from WIn NT to XP. THe XP Pro is being run under a VNWARE
Image. Two problems have emmerged

1. Access 2003 WIll not directly convert an AC97 MDB into 2003 version, it
scrambles the code, the solution is to convert it to Acc 200 first - very
strange

2. Using a reference to the MDW file I can open and use an Acc 97 MDB,
however, using the same MDW reference trying to open the same mdb under
Access 2003 so it can be converted to 2003 results in a 'User is not
authorized to open this data base for conversion or to enable it' type of
message. Why is Access 2003 interpreting the security settings differently
than Access 97 ?

 

[Albert D. Kallal]

We are upgrading from WIn NT to XP. THe XP Pro is being run under a
VNWARE
Image. Two problems have emmerged

1. Access 2003 WIll not directly convert an AC97 MDB into 2003 version, it
scrambles the code, the solution is to convert it to Acc 200 first - very
strange

I have converted some VERY extensive a97 applications to a2003..and it went
without a hitch. A few things:

Does, (or did) the a97 application compile correctly in a97...could you
create a97 mde files? Often, what happens is that a97 application has all
kinds of bugs, errors etc in the code. While it runs, conversion requites
that the application can compile. You should first try a compact, and a
repair. and then also try creating mde, or at least making sure the code
compiles. If the code compiles ok..then the conversion to a2003 should go
ok.

2. Using a reference to the MDW file I can open and use an Acc 97 MDB,
however, using the same MDW reference trying to open the same mdb under
Access 2003 so it can be converted to 2003 results in a 'User is not
authorized to open this data base for conversion or to enable it' type of
message. Why is Access 2003 interpreting the security settings
differently
than Access 97 ?

Perhaps the logon name you are using is different then the owner/creator of
the original mdb?