General error with migration 97 to access 2003

[Jordan2000]

In the company whe are migrating from NT4 with Access 97 to a XP And office 2003 enviroment.

This couses some serrius Isues.

one of them richt no is a Multi usser DB. 2 systems of XP and only one of them is able to run the DB. both instalations are the same. ... the DB is tested on more XP systems. but so als it seems only one person is able to run the DB at a time..

But a few can't run the DB at al.

the Software on all systems is the Same Image so there is no diference between OS and Office.

Who already migrated from 97 to 2003 and had isues with migrating..
like these.

.. on the department whe have 15 + diferent DB's in 97. and the Main developers of these DB's ore the IT department is not going to fix this.

 

[ghudson]

Likely cause is the PCs in question have "missing reference" errors. Search the forum for the issue has been discussed in many other threads.

 

[The_Doc_Man]

1. When migrating from AC97 to at least one higher version: You run into a lot of issues because it was the next version after AC97 that introduced the ADO confusion. Plus the issue that many of the .DLL files changed names to reflect changes in versions.

2. When migrating from NT4 to XP, you have to know which Service Pack you are on because XP SP 2 tightened up security a LOT. Enough that it often breaks Access. So you need to read the release notes if you have an XP that is SP 2 or higher.

3. For shared DBs, you need specific permissions on the shared folder. You should shoot for:

a. Though the folder might not be the top level of the drive, the fewer sub-folders you have to traverse, the better, for security and efficiency reasons.

b. All users of the DBs need permissions in the "MODIFY" (basic) category for the folder and all files therein.

c. All users need Advanced permission PASS THROUGH for any folder "above" the working folder.

d. The .MDB, .WKG, and .LDB files need to be in the same folder.