Referential Integrity 1

[Minkers]

When my supervisor, on a Windows XP machine, enters data into my form he gets an error that the subform record cannot be created because there is no corresponding record in tblECN. This is after he has entered data into the main form. When I enter data to the same form, or my co-worker enters data to the same form we both have no problem. Our computers however are on Windows 2000. I added a save command when entering the subform to save the data on the main form but that does not fix it. All three machines have Office 2000 on them.

On a side note, when viewing the database originally on my supervisor's computer it would not open. It was missing the library FILEMGMT 1.0 data library. I disable the library from my Windows 2000 machine and he can now load the database. I checked the database throughly on my Windows 2000 machine for any problems relating to removing that Library but I found nothing.

How can I fix this?

Thanks in advace!
Minkers

 

[grande]

Your supervisor is probably just a nub.

 

[Minkers]

I don't understand what you mean. I was there when he was filling out the form and have replicated the steps he took on my windows 2000 machine. I get the error when I am using his machine as well, but not using my windows 2000 machine. I have attempted to troubleshoot this as far as possible, but other than the OS on the machines there is no discernable difference.

 

[willir]

There are known issues with Opportunistic locking which may be at fault where write caching may prevent a current access to the database. If this is a problem, it is normally a problem between users, not for one PC.

However, apply the latest service packs for Windows XP and Office.

 

[grande]

I was just making fun of your boss, just jokes.

Yeah, I dunno. I've always thought that XP licked balls, so I wouldn't be surprised if that was your problem.

 

[Minkers]

From what I have read Opportunistic Locking might be the problem. Can this problem be circumvented by the Front End being on a user's computer and linking to a networked back end? This is how the setup will be eventually, but we have been accessing both files across the network since the database is in testing phase.

Also there are other databases used across the network and I have never heard it should be a more common problem if it is Oppertunistic Locking. Are there any other potential causes?

What I am seeing when looking in the database is that the record that the supervisor created is there, but it still gave him the "Cannot enter record because a record is required in tblECN" I verified that it happened even when no one else was in the database.

This is a screencap of my Advanced Options for the database Perhaps there is an error there though from what I have researched is should be ok.

Thanks again for the help!
Minkers

 

[willir]

Minkers

Opportunistic Locking is at the system level regardless of application. It is a Catch-22 where it improves performance, but murder on databases.

Although write-caching has been a problem for years, the new service packs apparently address the problem -- as I understand it, performs Opportunistic Locking on regular files, but does not cache writes to the database -- best of both worlds.

This server caching needs to interface / communicate / synchronize with the client. Which is why the services packs needs to be applied to the desktop.

More links...
How to keep a Jet 4.0 database in top working condition

How to keep a Jet 4.0 database in top working condition in Access 2000

Configuring opportunistic locking in Windows

Configuring opportunistic locking in Windows

Richard