Locked records

D

dpearson

I am having a bit of an annoying problem with my Access application.

The data is held on a SQL 2000 server with Access front-end.

I have a form (Form A) used for editing records, this form is launched
from a command button on another form (Form B) and filters to a
sepcific records on Form A dependant on the record in Form B. Nothing
special here I use this technique all over this application.

Form A opens up and displays the record I want but when ever I make a
change and try to exit the form or save the record I get the following
message:

"The record has been changed by another user since you started editing
it. If you save the record, you will overwrite the changes the other
user has made. Copying the changes to the clipboard will let you look
at the values the other user entered, and then paste your changes back
nig if you decide to make changes."

The [Save Record] button is greyed out but the [Copy to Clipboard] and
[Drop Changes] buttons are available.

If I click on [Copy to Clipbaord] I then get another error message:

"Runt-time error '3197':
The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

The thing is that this is a test system and I am the only user using
the tables/form etc invloved.

I have checked the default value setting is empty for all the controls
on the form and that I have not VBA updating any fields upon opening.
I even created a new form linked to the table and just put all the
fields on, saved it as Form A and then tried it but got exactly the
same error so I know that there was not VBA or default value
interference involved. I have also tried recreating the SQL table and
re-linking the the fron-end bu still got the same option.

I use this technique all over in this application for other tables but
never have I come accross this error.

I am hoping somebody knows the answer to this one.....

Regards

David Pearson
 
D

dpearson

UPDATE:

I cannot edit records direcotly to the table using Access. I get the
same error. So this is either a config error on SQL that I cannot
find or my table is corrupt somehow.
 
D

dpearson

ANOTHER UPDATE:

Just to let you all know I got around the problem.

In the end I imported the table into Access from SQL. Renamed my SQL
table and then upsized the imported table back to SQL. I then removed
the original SQL table and linked my Access app the the newly upsized.
one. This resolved the issue.

Thanks to anyone who read my port.
 
C

chuck.billings

ANOTHERUPDATE:

Just to let you all know I got around the problem.

In the end I imported the table into Access from SQL. Renamed my SQL
table and then upsized the imported table back to SQL. I then removed
the original SQL table and linked my Access app the the newly upsized.
one. This resolved the issue.

Thanks to anyone who read my port.

Thank you for your post! I read tons of different possibilities and
tried them all but this one worked for me!! Curious as to why but too
tired to care right now!!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top