Updating Split DB: My user doesn't see changes in my new form in shared folder

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

solved

Edited to Add:Now solved -- she was not looking in the same file location, user had a version stored locally...

Which is exactly how it should be...each user has to have a copy of the Front End on their machine! Having multiple users sharing a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior!

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally dozens and dozens of reports of split databases, using links to a single Front End, causing these kinds of problems, as well as massive data loss! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Linq ;0)>

Hope this helps!

The problem with making anything foolproof...is that fools are so darn ingenious!

Thank you! re: split databases

Originally Posted by Missinglinq

Which is exactly how it should be...each user has to have a copy of the Front End on their machine! Having multiple users sharing a single Front End, on a network drive, is the sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior!

Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past ten years have seen literally dozens and dozens of reports of split databases, using links to a single Front End, causing these kinds of problems, as well as massive data loss! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again!

Linq ;0)>

Thanks so much for telling me this. I really inherited this setup, am used to another system altogether, and am still learning. It sounds like I inherited a setup with best practices, even if I'm still learning everything there is to know about it.