Using access on a Network Problem

[wchelly]

We've been sharing a database with another office on the east coast, while we are on the west coast. The back-end resides here with us and we have been doing this for about a year and a half. While it doesn't always work great or speedily, it has worked and updated data so that we can share information.

Recently, we've had a problem with the data. What we've found is that when they update the file, make changes, add, or delete a record, they can see their changes, and if they navigate to the back-end file....they can see the changes there in the back end file. We can do the same when we make changes. However, we cannot see each other's changes. If a record is deleted on the east coast, we still see the record unless we delete it. Same if we add or change a record. I don't understand this because theoretically we are working in the same file. But....it's like the folder is duplicated somehow and we each have separate copies, but we don't.

Why might this be happening? And why would it be happening now and not before?

 

[AccessMSSQL]

Are you both navigating to the same back-end file? Sounds like not at this piont. Check your linked tables on both networks. Make sure you are both still pointing to the same copy of the data file. Check your network drive mappings on individual machines. Search east coast network for duplicates of the data file. Check your network for duplicates of the data file. You will just need to do some further investigation. The only explanation is that you are both pointing to a different data file.

 

[wchelly]

Yes, I renamed the back-end, relinked everything....sent out new version. I've connected remotely to her machine and watched her navegate to the back-end. She follows the same path. But I agree, we must be connecting to different files. The only thing I can think of is that it is somehow mirrored. I also learned minutes ago that another access database began having similar issues around the same time frame. This must be a server/system issue.

 

[wchelly]

Warning: When converting a database to 2010 from and older version

I converted the back-end of this database from Access 2003 to 2010 before this problem began. Unbounced to me, Access 2010 has a "caching" feature which is not available in 2003. When I converted, this somehow got turned on, and my database appeared to be storing data in TWO back-ends. However, I believe it was caching the data but not updating the back-end. I've changed the settings, it appears to have solved the problem, but we'll see tomorrow if it continues to work correctly.

 

[AccessMSSQL]

Glad you figured it out. Thought I knew everything about 2010 but guess not. Thanks.