Search results

nice !!! any significant delay when the databases are copied down? users need to be given any kind of heads up as to what's going on behind the scenes?

point taken .... safe to say then that you're fairly confident that my corruption problems are due to multiple users sharing one database?

G, thanks for the comments. do not have the db split. i have indeed seen that approach recommended many times over and maybe i'm just being stubborn but it just seems to me to be an extraordinarily inefficient way of doing things. i keep avoiding this due to the time and effort expended...

I manage and maintain a few multiuser Access databases (each one has no more than 5 users at any given time). One occassional nagging problem that I encounter is my db being placed in an 'unuseable' state (i.e. db needs to be repaired before continued use). I am assuming that this problem is...

Have a database being used in a multiuser on evironment that, on occasion, is placed into an 'unusable' state and requires kicking all the users out and repairing it. Wonder if some error handling might prevent this from happening. Thoughts? Opinions? Thanks

I have a front-end and a back-end which both reside on the server. The tables are simply linked. Is there a better (read, more efficient) way to do this? Have always thought that performing the link thru code or ODBC would be more efficient but thought I would check in with experts. thx