Form Occassionally Disallows Record Edits

mjdemaris

Working on it...
Local time
Today, 02:45
Joined
Jul 9, 2015
Messages
426
Hello all,
The form in question opens from a click event on another form - showing the details of an order, with a subform that shows the line items.
Everything has been working fine until today (about a year or so).
I have 4 records that I cannot edit.
When the form opens, it checks who the user is, and grants permissions based on their level of authority. If a record edit is needed, a button is provided that will change the AllowEdits property to True.
However, these 4 records cannot be edited even though it is true.
I have imported the two tables into my development database, and I CAN edit them there. So, I compiled the database, compacted and repaired, distributed the dev copy to the network...and I still have the same problem.

I have the form record lock set to edited record, as well.
Only thing that I have noticed is that someone may have been using the network copy of the front end, instead of the one that should be on their local machine, because I found a .laccdb file, which I deleted before redeploying the dev version to production.

Thoughts?
 
Update:
I logged off all users, copied the backend to my desktop and a backup folder, deleted the server copy, ran a compact and repair, and tested.
The issue with those 4 records is gone, however, another issue popped up. This time, one field in one table refused to take data.
I disabled the code that added data to that field, and everything worked fine (that I tested anyway!). Then, I imported that one table into another database, deleted it from the backend, re-imported it into the backend, and enabled the code that inputs data into that one field. So far, everything works like normal.
The table and field in question is a Login table - storing who logs in and when, and the machine name. For some reason it refused to continue accepting data. Something happened when I ran that compact and repair, but I do not know what.
Consider the problem solved, but the cause(s) still remains a mystery.
 
Its very possible that data got corrupted if someone (or several people) opened the network copy of the front end.

Are you aware that the laccdb file is a standard text file which you can open in Notepad?
It will tell you the workstation that was connected to that accdb file.
So you will know who to blame if it happens again.... :)
 
You dont set Edited records on Record Locking on multi user env. It will lock out other user when they need to edit the record. You allow access to take control of the record when it got save using No record Lock.
 
@ridders: That is very cool! thanks.

@arnelgp: Are you saying that I should not set the Record Lock property to Edited Record in the form? Won't this allow another user to edit the same record I am?
 
Yes it will.
Whoever is the last who saved the record will be presented by a message that the record has been changed and will ask if you want to save your changes.
Something similar if you have worked on a shared excel workbook.

Since the scenario is multi user, you dont really know what are the activity of the other users.
Worst he us doing bulk update using query. Then you have the record lock. A deadlock is stablish on the other user and his update is nit progressing because access is waiting for the lock to be released.
 
Bulk updates are not used here, except by me. Everything else is single record use only. I don't want two users changing the same record at the same time - this could cause problems. Each record is edited by a form, so when the user is done, they close the form.
So far, I have not had a problem with someone leaving a form open for a long time (not that I am aware of, anyway).
 

Users who are viewing this thread

Back
Top Bottom