Another user has edited the record

I have an access front end and a SQL 2000 backend. In the backend I changed a ntext field to a text field using a script and it then placed the field at the end of the field list. when I try to make a change to a record on the front end I get an error that another user has edited the record and must re-edit it. I can then make a change to the record. If I do a refresh I then get the error again. I then moved the text field back into it's original position and the error went away. Can anyone explain this?Hi Doug:
I think if it is possible, please show use your error ID, then we can
get more information about the error.
Best Wishes
Wei Ci Zhousql

Another user has edited the record

I have an access front end and a SQL 2000 backend. In the backend I changed
a ntext field to a text field using a script and it then placed the field at
the end of the field list. when I try to make a change to a record on the f
ront end I get an error tha
t another user has edited the record and must re-edit it. I can then make a
change to the record. If I do a refresh I then get the error again. I then m
oved the text field back into it's original position and the error went away
. Can anyone explain this?Hi Doug:
I think if it is possible, please show use your error ID, then we can
get more information about the error.
Best Wishes
Wei Ci Zhou

Another record locking issue...

Hi all,

I'm working on a Planning Databse for a factory that allows jobs to be allocated to machines and to be given a priority. This info. is displayed on an Access 2000 form e.g.

MACHINE ONE MACHINE TWO
Priority Job Number Priority Job Number
1 J111 1 J654
2 J562 2 J865
3 j231 3 J821

Both the Production Manager and the Factory Manager have this form open at all times. The problem is this, if for example the Factory Manager changes the priority of a job on his PC, the change is not shown on the Production Managers PC (cos' his screen has not been refreshed with update) The Production Manager therefore has old data on his screen and could mistakenly think that the job priority had not changed at all...
I have managed to write some VBA code to get round this but I was wondering if there was any way of 'pushing ' changes to the front-end when they are made or of using record-locking etc. to achieve the same affect...

Thanks
MThat situation shouldn't happen. However, review optimistic and pessimistic locking. Pessimisitic should definitely work if you're having problems with optimistic.|||Give them a refresh button?|||I have already implemented a refresh button but every now and again the users forget to press it and this causes problems. Also tried using the Access Timer Interval to refersh every n seconds but that caused other problems that I won't go into here.

Sorry I didn't reply sooner as I was off ill yesterday :-(|||The only way that I can see that would resolve your problem is implementing some kind of refresh interval on the front end, as the refresh button aproach apparently didn't work!

The problem with "forcing new entries" is basically that you actually retrieve data from the db, and thus it's kind of difficult to force a re-fetch from the db side...|||Listen, I can send you some monkeys that can click the refresh button for you...|||Hey guys,

I've just realised that i never mentioned the back-end is a SQL Server 2000 database!!! Basically, I just don't understand record locking well enough and will have to go and do some research...thanks for all your inpute.