Re: recordset record locking

[bob lambert]

Mike

Thanks for the info. I have really been struggling along. The article is interesting, but I am afraid I don't quite get it. When I originally coded my app in Access, I never had to worry about cursors, so I am struggling to understand the when and why part.

First, my db has all INNODB tables that reside on the server in mysql. Some temporary tables that are used locally (in the access front end) are not INNODB I think. And I do have both primary keys and foreign keys in the tables. I checked for issues like null bit fields, but do not think I have that issue in this particular table. I do have some spare int fields that I allow to be null, otherwise all other fields are not null constrained. When I save some data the first time, some of those fields get a 0 in them to satisfy the not null condition. Its those fields I am attempting to go back and populate on my 2nd edit of a record. I am testing / building up this app on my home network, so I can simulate someone accessing an ip address to access the data. Eventually I will replace the ms access front end w/ a php based web interface. But I digress ....

If my db app is such that an individual user is the only person accessing / modifying data (may grant viewing/output capability to other users later), then I am thinking that means I could benefit from client side cursor control (assume that since I have done nothing yet, I am defaulting to server side). If that is not the casel, then I don't get how you prevent 2 users from stepping on each other.

I will carefully read the article and attempt to use client side cursor and get back to you.

Thanks
Bob Lambert