table lock

[alvinmcg]

I am having a problem with my current project. This is in Paradox 8 and in use on a network. I have several lookup tables for key fields. One in particular appears to be causing a lock on the master records and we get the following error:

This record in LOOKUP TABLE.DB is already locked by USER NAME.

The connection is that if a user is editing a master record, then each other record with the same inspector (the lookup table field) will also be locked.

I can not see how this is locking each and every other record with the same lookup table value. Any ideas?

 

[hcts]

Do you have referental integerty setup on these tables?

 

[alvinmcg]

Yes, I believe I do. However, currently the tables are unavailable as the VAL files have been corrupted. Our IT department is restoring same from a backup.

The lookup field is an inspector's name. Each project has only one assigned inspector. Could this referential integrity cause the type of error we are seeing?

There are many tables in the system. Some are one to one. Others are one to many. Only the Inspectors table appears to be causing the problem.

Thank you for your advice.

Alvin

 

[hcts]

I don't know if the ref int is causing your problem, however I removed all the ref int from my app about 5 years ago because of performance and stability problems. I went in and coded the applicable changes into my forms.

Another problem could be if the Inspector form that you are changing the information on also has the child tables attached to the data model and Ref Int is turned on. You might try either turning off the ref int or creating a table without the child tables on it.