unable to delete/update/add data

[js]

The MDB is on a network shared drive. The tables are external linked
tables from SQL Server. I ran into update problem even when I was the
only user on our network using the MDB at that time. It said "The
Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."
Does anyone know why this is happening? I compacted and repaired the
database and still ran into the problem. Thanks.

 

[js]

One more observation. This happened when I modified the table
structure in SQL Server and used Link Table Manager to refresh the
linked table.
I even deleted the table in Access and relinked it from the SQL Server,
I still got the problem. Thanks.

 

[SJ]

Have the tables got any triggers on them.? because it sounds as tho its
telling you what the problem is... the "another user" might be be a system
thing, like a trigger or something. maybe you changed the data at the
front end and a process running in the SQL Server is acting on that....

 

[Van T. Dinh]

1. Yes, you definitely should refresh the linked Tables in the Front-End
whenever you modify the Table Structure in the SQL Server BE.

2. Not sure if this will fox your problem but try:
(i) Make sure no one in in the database.
(ii) Go to the directory that holds the MDB. If there is a file
{SameDatabaseName}.LDB, delete it.
***Make sure it is the LDB, NOT MDB***

3. If this is a multi-user application, you should provide a separate
Front-End for each user, preferably on his / her PC. To help main the
copies of the FE up-to-date, you may like to check out Tony Toews' "AutoFE
Updater" at:

http://www.granite.ab.ca/access/autoFE.htm

 

[Van T. Dinh]

I meant to type:

"... To help maintain ..."

 

[js]

No, this table is just plain simple table that is upsized from ACCESS.
There is an auto number field on the first column as the record key. It
seems to me that some thing is preventing the delete of any NEW record
I added. Strangely, it allows me to delete any record that exists
before the database is upsized. Any suggestion?

 

[js]

I fixed the problem. It turns out that the SQL Server bit fields need
to be default to 0 for linked tables with Yes/No columns in Access to
work.