Clipster said:
Using externally linked tables, (1 or 2 tables), we almost always end up
crashing after starting up access. Windows XP, Access 2000.
First, 100% cpu use is not uncommon, but Access is very good about yielding
control to the system so other work is done without interference. Second,
the subject does not seem to have any relationship to the problem you state.
There is no inherent problem with using linked tables, either on the same
machine or on a shared folder on the same LAN. Many others, and I, use that
arrangement every day without problems.
"Crashing" is not very specific, and neither is "end up". Could you clarify,
with some specifics? How many users? Are multiple users logged in to the
same front end or monolithic database? Are there other tables internal to
the application? What are you trying to do when it "crashes"? What are the
symptoms of the crash?
There are at least three Service Packs, and some additional updates, to
Access 2000.My recollection is that there is one Service Pack and numerous
updates to Windows XP. There are eight Service Packs to the Jet 4.0 database
engine. Do you have them installed? That may not correct the problem, but
it would be a first step that would eliminate the possibility of an-already
corrected problem being the cause of your difficulty.
Larry Linson
Microsoft Access MVP
