URGENT!!! sql server - adding and editing records

[lala]

Hi guys
i have this problem
i just converted to SQL and here's what happens
my front end is in MS Access
when i try to add a record and save it in Access, i'm fine
but if i want to come back to that record and make changes or delete it - errors
i can't delete it, it says Jet engine stopped because you or another user trying to edit same record at the same time
i'm the only user right now
i can't edit it either - it gives me the box - you and another user changed same data at the same time, and save is greyed out, i only have option to DROP CHANGES or COPY TO CLIPBOARD

now if i try deleting or editing records already in the database - everything is fine

anyone????
i have no idea what's going on

 

[CyberLynx]

There could be a number of things causing this but try this first:

In the Database Main Menu Bar select Tools | Options and then select the Advanced tab. Make sure the Open databases using record-level locking Check Box is checked.

Also check out this thread.

.

 

[lala]

That's not my case
My database has record level locking
and the subforms - it worked before when it was on access backend
So the subforms are fine

Anything else?

 

[Pat Hartman]

Your code is causing the problem. Are you updating records of the RecordSource behind the scenes in the form?

 

[lala]

Your code is causing the problem. Are you updating records of the RecordSource behind the scenes in the form?

you mean, do i have code that updates some boxes automatically?
yes, i do
i will check it tonight

but then question
how come i can make changes to and delete records that are already there?
this problem is only when i add a record, save it and then try changing or deleting it

changing or deleting old records is not a problem

also, i can change or delete those records directly from SQL without a problem
this only happens in MS Access


thank you, Pat
i read many of your messages and learned a whole lot
one night i just filtered by your name and read a few hundred, it's like an MS Access book


and i appreciate your help with this problem

 

[Pat Hartman]

If the current record is dirty and you run ADO/DAO code or an update query behind the scenes, you will have a conflict. If you MUST do background updates, make sure that the current record is saved first.

 

[lala]

come to find out
i had BIT fields in there (in access there's the Yes/No fields) and in SQL the settings have to be DO NOT ALLOW NULL and default value or binding has to be 0
and then the same thing has to be done on the Access side, all the checkboxes have to get a default value of 0

 

[lala]

how do i mark this thread as solved?