I have searched the forum and my problem does not appear to be uncommon - but there appears to be no definitive solution. Any futher help would be appreciated.
The problem is on opening the message "the database needs to be repaired ....you may have quit access whilst a db was open etc." appears
this is happening frequently (every day this week) the database has been fine for two years.
It is easlily fixed but a nuisance getting everyone to exit the db
My system
1 Windows 98
2 On server plus 10 users
3 less than 7MB size
4 plenty of disk space / power
5 compacted every month up until recent problems
6 Database is not split
7 Users are aware of correct method to exit db
One point to mention is that 1 computer on the network is now an XP machine - but this was added about a month ago - no problems initially.
I have read that it could be worth splitting - I have avoided this in the past as again reading through previous posts the cons outweighed the pros for the excercise.
I have also seen comments on "compiling" but unsure as to what this is about exactly.
Many thanks for any help / ideas
The problem is on opening the message "the database needs to be repaired ....you may have quit access whilst a db was open etc." appears
this is happening frequently (every day this week) the database has been fine for two years.
It is easlily fixed but a nuisance getting everyone to exit the db
My system
1 Windows 98
2 On server plus 10 users
3 less than 7MB size
4 plenty of disk space / power
5 compacted every month up until recent problems
6 Database is not split
7 Users are aware of correct method to exit db
One point to mention is that 1 computer on the network is now an XP machine - but this was added about a month ago - no problems initially.
I have read that it could be worth splitting - I have avoided this in the past as again reading through previous posts the cons outweighed the pros for the excercise.
I have also seen comments on "compiling" but unsure as to what this is about exactly.
Many thanks for any help / ideas
