We have an Access database which keeps getting corrupt. One of the tables have
more than 500 000 entries in it.
I thought of converting to SQL 2000, but the access DB has Select and Update
queries in it, and I can't seem to accomodate it.
Any suggestions.
Thanks.
Paul.
Paul
Have you looked into how/why the corruption is happening?
What is the design of your database? Do you have a split database, with a
copy of the front-end .mdb file on each user's PC and a single back-end .mdb
on a server on your LAN? Are you working over a WAN? Do you have a NIC or
a router or a cable that's gone bad?
What are you doing ... mostly data entry or mostly data lookup? How many
users are simultaneously hitting the database.
Before you take on the migration, consider ruling out other causes...

Signature
Regards
Jeff Boyce
Microsoft Office/Access MVP
http://mvp.support.microsoft.com/
Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/
Microsoft Registered Partner
https://partner.microsoft.com/
> We have an Access database which keeps getting corrupt. One of the tables have
> more than 500 000 entries in it.
[quoted text clipped - 7 lines]
>
> Paul.
Camper Joe - 18 Sep 2006 13:48 GMT
VB Front End
Doing both alot of reads and writes
about 4 simultanious users accross a lan.
Paul.
> Paul
>
[quoted text clipped - 23 lines]
> >
> > Paul.
Jeff Boyce - 18 Sep 2006 14:59 GMT
Corruption is commonly a symptom.
4 simultaneous users, doing read/write against an Access/JET back-end should
not, in & of itself, cause corruptions. Consider checking the other
possibilities I mentioned.
Or you could migrate the data to a different (i.e., SQL-Server) back-end,
only to find you are still having issues!

Signature
Regards
Jeff Boyce
Microsoft Office/Access MVP
http://mvp.support.microsoft.com/
Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/
Microsoft Registered Partner
https://partner.microsoft.com/
> VB Front End
>
[quoted text clipped - 31 lines]
> > >
> > > Paul.