Access 2003 corruption problems

[solex]

Hello,
I have a suite of Access 97 applications that I recently upgraded to 2003 .
The applications consist of several MDE front ends to a set of corresponding
MDB backends. Most of the apps are inter-related via table links. I also
have about 10 concurrent users up by 5 in the past few weeks.

The MDE and MDB files are on a network share on a Windows 2000 server. The
problem I am having is that frequently the users will get an error when
starting up the main application: "repair my open database and restart
Microsoft office"

A backup is created and then the database is fine. The database size also
increases greatly. This application is not heavy on the transaction side
(CRM) but use mainly for lookups. I am on Windows XP but all other users
are using Windows 2K professional. I tried changing the short cuts to use
the UNC but this did not help.

Any suggestions would be appreciated!

Thanks,
Dan

 

[Douglas J. Steele]

Each user should have his/her own copy of the front-end, preferably on their
hard drive.

Are you sure about the quality of your network cards? That's probably the
number 1 cause of corruption.

See what Tony Toews has at http://www.granite.ab.ca/access/corruptmdbs.htm
for other causes of corruption.

 

[solex]

Doug,

Thanks for your response, but why do the users need to have the front-end on
their hard drive? This was not the case with Access 97/2000 has something
significantly changed? This problem presented itself when (a) I upgraded to
2003 and (b) we have twice as many users.

Thanks,
Dan

 

[Douglas J. Steele]

Even with Access 97, they should have had their own copy on the front-end.

Sharing a front-end is a common cause of corruption. Having the front-end on
the server rather than the hard drive means much more network traffic, since
the form definitions and such need to be transferred across the wire with
each invokation.

 

[mohammed]

Hello,
I have a suite of Access 97 applications that I recently upgraded to 2003 ..
The applications consist of several MDE front ends to a set of corresponding
MDB backends. Most of the apps are inter-related via table links. I also
have about 10 concurrent users up by 5 in the past few weeks.

The MDE and MDB files are on a network share on a Windows 2000 server. The
problem I am having is that frequently the users will get an error when
starting up the main application: "repair my open database and restart
Microsoft office"

A backup is created and then the database is fine. The database size also
increases greatly. This application is not heavy on the transaction side
(CRM) but use mainly for lookups. I am on Windows XP but all other users
are using Windows 2K professional. I tried changing the short cuts to use
the UNC but this did not help.

Any suggestions would be appreciated!

Thanks,
Dan

 

[Dirk Goldgar]

Even with Access 97, they should have had their own copy on the
front-end.

Agreed, but the change that came with Access 2000 from a modular project
to a monolithic project made this much more important, I think. I don't
know if this is the cause of Dan's problems, but it wouldn't surprise
me, since Dan is working, and presumably developing, on a different OS
version from his users.

 

[Tony Toews]

Thanks for your response, but why do the users need to have the front-end on
their hard drive? This was not the case with Access 97/2000 has something
significantly changed? This problem presented itself when (a) I upgraded to
2003 and (b) we have twice as many users.

FWIW we noticed a big increase in the number of corruptions when
sharing an A2000 FE MDB/MDE compared to A97. It's quite possible
though that five users on A2000 sharing your FE MDB/MDE is ok most of
the time sort of but ten users would not be fine.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm