Record not allowed to update MSSQL BE

[Kenln]

I have an MSSQL back end.

One one form I add a record to the database. I can enter anydata that I wish at that time.

BUT... If I go to another record then back to it, I get the message the records is in use by another user. This also happens when I go to another form and try to enter any data into this new record.

I believe this is a timing issue and the cache/SQL/something needs to update (flush).

Is there anyway to get the record to update after it is inserted so it may be used on other screens?????

Thank you,

 

[boblarson]

Actually, it sounds like you might be having some code that is causing the conflict.

 

[Kenln]

Bob,

Even if I go to the linked table directly, no forms or code running,
I can add a record.
Move to another record.
Return to the new record.
I cannot edit this new record.

Of course after a while (I havent figured when or why) I can edit it fine. Also if I write a sql statement (insert or update) I can edit edit the query.

Once a sql statement is run, guess what? I can edit the record directly.
hmmm,

This is my first real attempt at using MSSQL. We are talking about moving or BE to it so I kinda need to figure this out.

I appreciate any help,

 

[boblarson]

I've not experienced anything like you're describing in my use of SQL Server as a BE and I have a fairly complex project I've been working on for the last 7 months in SQL Server/Access FE.

Perhaps you might also post the question here to get more possible solutions:
http://www.sqlservercentral.com/Forums/

 

[LPurvis]

Is this (as per your other question) from an ADP?
Sounds unusual - as I'm sure you'll have a Primary Key in this target table (hence the ability to append rows).
With such concurrency issues - I'd recommend creating a TimeStamp field in the table if it doesn't already have one. Access makes good use of them to determine genuine concurrency as opposed to apparent conflicts.

Cheers.

 

[Kenln]

Actually this is an mdb.
But... In the forum Bob sent me they talk about a TimeStamp helping Access determine when the records was last updated (for the latest).

So... I added a time stamp and have not experienced the problem for the last hour or so. I am going to work with this a bit, it may have (hopefully) solved the problem. Yeah!!

 

[LPurvis]

I'm glad their suggestion of a TimeStamp field helped you.