| re: .MDB lockes records in tables linked via ODBC to SQL SERVER 2k
Tables need to have a Primary Key, and a 'timestamp' field
(timestamp??? has the name changed for that type????).
Also, Boolean fields need to be not nullable.
Because of the way floats and dates are stored and used,
it may appear to Access/Jet that the record has been changed.
To stop Access/Jet from trying to compare data values,
you need to have a 'timestamp' field that Access/Jet will
use to see if any changes have been made to the record.
Because Boolean fields in Jet 3/Jet 4 are not nullable,
any null Boolean field is automatically converted to FALSE.
This makes it appear that the record has changed, even when
it has not.
(david)
<orentini@hotmail.com> wrote in message
news:1096026616.274369.70680@k26g2000oda.googlegro ups.com...[color=blue]
> Microsoft Access MVP's and other good people - please help.
> I've posted here before.
>
> I'm having some weird problems with *some* ODBC linked tables on my MDB
> (Access XP), located on a file server for which i have full
> permissions.
>
> The tables are stored on a SQL server 2000.
>
> The problem is that any user (including me) can add records to this
> table but *no one* can delete,modify,edit these records from the MDB.
> (Error message "Another user is editing this record, save ...")
>
> Editing of these records is possible only from the SQLserver (.ADP).
>
> this is a new problem (about 2 weeks), i've solved it temporarily by
> moving these bad tables to another file-server based MDB and linking
> them to the main MDB (not optimal to say the least).
>
> No one can tell me what's wrong, not even the main administrator.
> Any Idea?
>
> Oren.
>[/color]
| 
