M
Malcolm Mackay
We have an application which uses MS Access with ODBC links to SQL Server
tables. Recently we changed from Access 97 to Access 2002 and we find we are
now getting high rates of MDB corruption during development, particularly
when copying objects into MDBs. The MDB ends up in a state where it can't be
repaired or compacted and is essentially unusable. This program MDB is quite
large, about 50MB, and has quite a lot of objects, about 1,000 forms, tables,
queries, reports and modules.
We have applied the most recent service packs for Office XP and Windows XP.
So the questions are:
Is the size of the MDB and number of objects a problem in Access 2002?
Are there desktop configuration settings that can minimise or eliminate
these problems?
Are there do's and don'ts in development procedures that can minimise or
eliminate these problems?
Is Access 2002 inherently less stable than Access 97?
Any help would be appreciated.
tables. Recently we changed from Access 97 to Access 2002 and we find we are
now getting high rates of MDB corruption during development, particularly
when copying objects into MDBs. The MDB ends up in a state where it can't be
repaired or compacted and is essentially unusable. This program MDB is quite
large, about 50MB, and has quite a lot of objects, about 1,000 forms, tables,
queries, reports and modules.
We have applied the most recent service packs for Office XP and Windows XP.
So the questions are:
Is the size of the MDB and number of objects a problem in Access 2002?
Are there desktop configuration settings that can minimise or eliminate
these problems?
Are there do's and don'ts in development procedures that can minimise or
eliminate these problems?
Is Access 2002 inherently less stable than Access 97?
Any help would be appreciated.