I'd try comp.databases.sql-server but it looks like a SPAM factory
there...

I added 3 new fields to a SQL table. I can edit data in SQL Server
just fine. However, when I try to edit the data in Access (the tables
are linked to an Access front-end), I get "This record has been
changed by another user since you started editing it. Etc..."
Obviously it's a locking issue. I know when you add fields to a table
that it literally drops the table and then recreates it with the new
fields. I'm wondering if the permissions get reset or something when
that happens? I know for a fact that no one else is in this table,
it's on a DEV server and I'm the only one in this database. Any ideas?

On Fri, 3 Dec 2010 11:19:39 -0800 (PST), ManningFan
<manningfan (AT) gmail (DOT) com> wrote:

No it's not obvious. Do your tables have a TimeStamp aka RowVersion
colum? Access really likes those.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

On Dec 3, 2:23*pm, Tony Toews <tto... (AT) telusplanet (DOT) net> wrote:
Ha! You're right, I was "obviously" wrong. One of the new fields I
created was a BIT (it's a Yes/No field), and it turned out Access
didn't like it. Changed it to a Varchar(1) and everything was fine.

On Fri, 3 Dec 2010 11:35:19 -0800 (PST), ManningFan
<manningfan (AT) gmail (DOT) com> wrote:

Oh yes, I'd forgotten about that one. Although making it an integer
or byte field might be somewhat better.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/

wow it must really suck to have all these extra limitations.

you DO know that if you moved to Access Data Projects, you wouldn't have to worry about any of this bullshit, and you can just build forms and reports directly against sprocs without any of this linked tables bullshit?

wow.. so now.. every single SQL Server table needs an extra column.. just to work with Access?

What does -that- do to performance?

Oh yah.. you don't know anything about performance because you only work on baby-sized databases, huh?