Coversion from 2002 to 2003?

[Guest]

When I give my mdb created in 2002 on an XP machine, to a 2003 users on a
Windows 2000 Professional machine, the file will not open. The process stops
with an error message that refers to VBE6.DLL. The file never opens/converts.
The resolution was to create a blank mdb and import the objects.

FYI,

There were missing references to MSGraph11 and MSCOMCTL.OCX which we reset
in the blank mdb. Why did the file not open on the 2003 Access machine?

 

[Steve Huff]

If there where missing references on the new blank mdb copy which I assume
was created on Win2k with Access 2003 it sounds like that install has
problems from the beginning, not necessarily you database specifically.

 

[Guest]

Below is the first few line of the error.
also Will sp-3 update vbe6.dll to 6.4.xx.xx"

Any info will be greatly apprecited.

AppName: msaccess.exe AppVer: 10.0.4302.0 ModName: vbe6.dll
ModVer: 6.3.91.8 Offset: 00058baf

 

[Allen Browne]

Broken references, or references to the wrong version can certainly cause
crashes.

Additionally, A2002 uses a different binary for the compiled code than
A2003. Even though the file format is the same, the binary is different, so
an A2003 mde will be reported as "corrupt" if installed on an A2002 runtime.

Whenever you switch version, it is therefore a good idea to explicitly
remove the binary by decompiling the database with the version you have been
using to edit it. That means entering something like this at the command
prompt while Access is not running. It is all one line, and include the
quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"
Then compact the database.

The procedure you took of recreating the database in the desired version and
importing everything is a good one. However, a decompile is also needed
sometimes, as importing can just import the corruption.

If one particluar module/form is corrupt, the undocumented
SaveAsText/LoadFromText can also help.

Make sure Name AutoCorrect is off:
http://members.iinet.net.au/~allenbrowne/bug-03.html

General guidelines for avoiding corruption:
http://members.iinet.net.au/~allenbrowne/ser-25.html

 

[Guest]

Odd that now when a /decompile is attempeted on the A2002 or A2003 we get the
dreaded

"Microsoft Access has encountered a problem and needs to close. We are
sorry for the inconvenience." that refers to "AppName: msaccess.exe AppVer:
10.0.4302.0 ModName: vbe6.dll
ModVer: 6.3.91.8 Offset: 00058baf"

 

[Allen Browne]

Okay: the database is corrupt. Try the SaveAsText approach.