Hello
Can anyone help?
I am using an Access 97 database with an Access 97 and 2000 front end on a network. There are about 15 concurrent users at any one time.
For the past 3 weeks now I've been having calls that the 2000 front-end is crashing on a regular basis. I'm talking about 10 ten times a day.
1) Standard message: Database is not a database or needs repairing. This message appears only on some clients but not on all and the database is still accessible for some users. After I kick everyone off by Server Manager and repair all is OK until the next time.
I have monitored this situation for about 2 hours with no database crash and I'm now at a loss. I am aware that a Dr. Watson error, CTRL, ALT & DEL to log out etc will cause the DB to crash but not this often.
Could it be something to do with:
a) Certain or Different Drivers,
b) Users having Access 97 and 2000 installed on their machine (I can't believe users are trying to open the 97 database on 2000 everytime),
c) Users are at present being coverted from NT to Windows 2000 -c ould this have an impact.
d) Users are currently logging into a new domain that has I'm told ceen created a while ago now.
Any help would be great! Is there an autorepair facility by the way?
Thanks
Dawn
Can anyone help?
I am using an Access 97 database with an Access 97 and 2000 front end on a network. There are about 15 concurrent users at any one time.
For the past 3 weeks now I've been having calls that the 2000 front-end is crashing on a regular basis. I'm talking about 10 ten times a day.
1) Standard message: Database is not a database or needs repairing. This message appears only on some clients but not on all and the database is still accessible for some users. After I kick everyone off by Server Manager and repair all is OK until the next time.
I have monitored this situation for about 2 hours with no database crash and I'm now at a loss. I am aware that a Dr. Watson error, CTRL, ALT & DEL to log out etc will cause the DB to crash but not this often.
Could it be something to do with:
a) Certain or Different Drivers,
b) Users having Access 97 and 2000 installed on their machine (I can't believe users are trying to open the 97 database on 2000 everytime),
c) Users are at present being coverted from NT to Windows 2000 -c ould this have an impact.
d) Users are currently logging into a new domain that has I'm told ceen created a while ago now.
Any help would be great! Is there an autorepair facility by the way?
Thanks
Dawn