R
Ravi
We have an Access XP database that run on our network at
Houston TX. We have a team of people at both India and
Houston TX accessing the DB. India team accesses our
network via Citrix server here.
When 2 or 3 people from India tried to use the DB, they
experienced "run-time error" message. So the Access XP
database terminated. When they went back to the DB, it
said "The database needs to be repaired or isn't a
database file".
So people in Houston repaired the DB. It ran normally.
And once again, when 2 or 3 people from India tried to use
the DB, the same error "run-time error" message showed
again. Then people in Houston had to repairer the DB. It
occurs randomly in our process about 3 times a day.
However, if Houston team is the only users for the DB, it
ran smoothly without any problem. How can we fix
this "run-time error" to prevent repairing DB so often and
have India team use the same DB at the same time? Thanks,
Houston TX. We have a team of people at both India and
Houston TX accessing the DB. India team accesses our
network via Citrix server here.
When 2 or 3 people from India tried to use the DB, they
experienced "run-time error" message. So the Access XP
database terminated. When they went back to the DB, it
said "The database needs to be repaired or isn't a
database file".
So people in Houston repaired the DB. It ran normally.
And once again, when 2 or 3 people from India tried to use
the DB, the same error "run-time error" message showed
again. Then people in Houston had to repairer the DB. It
occurs randomly in our process about 3 times a day.
However, if Houston team is the only users for the DB, it
ran smoothly without any problem. How can we fix
this "run-time error" to prevent repairing DB so often and
have India team use the same DB at the same time? Thanks,