Synchronization issue

[Freshman]

Hi all,

I picked up the following at one of our Clients.

They have 3 PC connected to the same Inhouse LAN Server.

All 3 PC have the same Front end and all linking to the same BE mdb file on their server
On 2 of the PCs, changes made to the data can be seen from either side.
But the 3rd PC is on it's own mission. Any data changes cannot be seen by the other 2 PC.

I did the following tests:
1. Exit the db app on alll 3 PCs
2. Run the app on each PC one by one. As you open them I can see the very same BE mdb file locking so I know they have to be linked to the same BE file.
3. I also re-linked each PC to the same BE mdb file just to make sure.

This Client has been using our app for many year and never had this issue until recently (it must be since a few weeks ago if we compare data entries on the PCs).

Could this be a security issue on the server that was implemented causing this?

There are no read-only or locking warnings or anything that indicates a problem with data capturing on the 3rd PC. All seems fine until you compare the data.

Any ideas on this?

Thanks

 

[marlan]

Hi,

See here, you should have a FE file on each machine. opening a single file on a common network location can cause file corruption.
When a file gets corrupted, all sorts of weird things can happen...

ATB

 

[Freshman]

@marlan - thanks for taking the time to answer.
My setup is as you suggest. We currently waiting for the Client's IT dept to create another shared folder for us to test with to see if it resolves the issue.

 

[Freshman]

Hi all, for what it's worth I;m going to give feedback.

It turned out that a few weeks ago the lady with the "3rd PC" went on leave but after a few days decided to work form home. She then called the IT guy and he helped her to setup a VPN connection so she can still work and connect to the Backend dataset on their server.
However somewhere in this process the IT guy clicked on "Offline" which means she was then working on some offline version. and when she got back her PC never really linked back to the dataset on the server and she happily kept working offline.
We ran a few queries to identify the missing records and all sorted now.
Wow this had me going for a while...