>I'm encountering a crashing problem (database inconsistency) with a shared
>Access 2002 database. I've split a DB into a front-end (sales.mdb) and
[quoted text clipped - 8 lines]
>tables for the 2-3 minutes that it takes to push orders? Or, if this isn't
>the best solution, can anyone help with this?
No, you should really deal with the fundamental corruption problem.
Corruptions about once a year at most are typical. Ideally of course
non are wanted.
Trouble is it can be a daunting task to figure out why there are
corruptions.
For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm
Tony

Signature
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm