Leif said:
The pain is the following:
1. Linked tables. I make a local copy of the production database if I want
to check on some issue with a form or report. With linked tables I meed
reset my links. With one database I don't. I've had problems in this area.
For some reason sometimes, in certain cases, I cannot relink all of them at
once. Only one at a time seems to work.
I and my clients relink tables all the time without any problems.
Whenever I ship them a new version the code automatically does the
relinking.
2. Forgetting to reset links such that the BE is not the correct database.
That's where I use a variety of techniques. If I'm working in an MDB
and linking to tables on a network drive I change the background
colour to red as a warning. As the users only ever use an MDE I turn
this off for them.
3. Slow as a dog. I did try establishing a permant link, all the usual
suggestions, still much slower then one database, in my experience.
Somewhat slower but there are a number of things you can do.
Access Performance FAQ page at
http://www.granite.ab.ca/access/performancefaq.htm
4. I keep a history of the database on each update, including the data.
With a split database this will be more work trying to keep releases straight.
Copy and paste in Windows Explorer twice.
I know the heavy hitters, such as yourself and Joan recommend it, but its
caused me nothing but grief.
And me. <smile>
Your description of how well things have worked in the past is quite
remarkable. Are you still running in A97?
Tony
--
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
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/