"RayPower" < XXXX@XXXXX.COM > wrote
> I'm having a system using Access 2000 as both front-end (queries,
> forms, reports & temp tables for reports) & back-end (data) with
> back-end running on the server. The application runs on the network
> with around 15 users.
> The back-end database is suffering from performance issues. There were
> several corruptions since few months & one major corruption & corrupted
> the MSysObjects table. Also, the system will run batch process that
> generate hundreds to thousands of records in the transaction table,
> which caused the transaction table being locked even though users just
> trying to add new transactions even though the database has been
> selected to use record-level locking. Furthermore, some queries are
> very slow as they query the transaction table which has over 1.3
> million records.
I'd suggest you do some searching at Tony Toews' webstite,
information and links on avoiding corruption and improving performance that
I know of, for an Access mutliuser environment. A couple of more sites with
good information are Jeff Conrad's "Access Junkie" site... look for posts by
him in this newsgroup and the microsoft.public.access... newsgroups, and
Albert Kallal's site... again look for posts by Albert -- I think he carries
the site address in his SIG line.
Microsoft Access MVP
> company of the group) to update all PCs to Office 2003. Is upgrading to
> Access 2003 help to get the system more stable/reliable? Is Access 2003
> not so easy to corrupt? Can we get true record-locking or still
> suffering from locking pages or even the whole table when adding
> hundreds of records?
Well, I feel more comfortable with Access 2002 or Access 2003, with all the
Service Packs and updates, than I do with Access 2000, with all its Service
Packs and updates. I've discovered quite a number of people who have
problems but have not got their IT department to apply the SPs and updates.