Hi
I'm a newbie to Access, and have been given an existing Access database to work with. We've exported the data into SQL Server, so we now have Access forms and queries linking to SQL Server tables.

This seemed to be working OK in tests. I've now copied in some live data (using an Append query in Access) and it looked OK. However, if I try to edit this data on a particular form, I get 'another user has edited this record ...' (even though I know no-one else is using the system yet). Furthermore, the 'save changes' button is disabled - so it's become impossible to update these records at all.

The Access db is set with Default Open mode = Shared; Default Record Locking = No Locks, and Open Database Using Record Level Locking = True. However, I understand that ODBC automatically assumes No Locks (ignores Default Record Locking) - this makes me wonder if I need to be changing settings somewhere other than in Access?

I'd be grateful for any help here, I've no idea where to start looking. As always, this has taken longer to set up than expected, so I'm under pressure to get it sorted yesterday.

Many thanks

Gibbers

Hi again

I've looked into this a bit more, and established:

The problem exists at the table level - I can't update records directly in the table (in Access). I can add a record in the table, but can't then delete it (or any other record)

I can update records, and add and delete records in the SQL Server Table (using EM as sa). I can also update records on the server using Query Analyser, when logged in with the same login/pw as I use in Access.

I've set a unique PK in the SQL Server table, and Updated the ODBC link - this has not made any improvement.

I'd really appreciate some help on this!

Thanks

Gibbers

Just so you know, I waited for an answer on this as well. Then did another search and discovered a similar issue with a different backend database. I went ahead and applied the change, and it did fix my issue with editing that table. This is what I gathered.

Your form/table has a Check box that its having an issue with. On the back-end database, change the field to int(erger), and it should work. Mine was set to bit, and apparently access doesn't like the 3rd option of Null. Let me know if that works for you, as I know it worked for me. :)

DJ

Something else I discovered last year while working on an Access/SQL Server project. When I set up Primary Keys on the SQL Server side, it brought Access to it's knees and caused all kinds of problems.

I ended up removing the Keys and Indexes, and performance increased dramatically. I also ended up adding a timestamp field to each table - I forget why, and I don't interact with it at all, but I think it helped each record have a unique identifier or something.

Mike

Mike
EchoVue.com