Very Computer

I am getting a Write Conflict when trying to modify a
record in Access97 that was written to the SQL Table that
is linked.  The record writes fine from the Form via SQL,
but I am not able to modify it once in.  The error is
stating that the record has been changed by another user
since i started editing it, although there is nobody else
using the system and the record is new...
Any ideas/solution would be greatly appreciated.

This happens because of the way row versions are checked (what was fetched
back to Access vs. what's currently in the SQL Server) when you try to
update a row, certain datatypes in the underlying SQL Server table can cause
the versions to appear different even if no one else changed the data.  This
can be fixed by adding a timestamp column to the SQL Server table that will
then be used for row version comparison.  KB article Q278696 explains one of
the situations that causes your problem.

--
Bob

------
Please do not send email directly to this alias. This alias is for newsgroup
purposes and is intended to prevent automated spam. I've been "encouraged"
to share this helpful information from our lawyers. This posting is provided
"AS IS" with no warranties, and confers no rights. You assume all risk for
your use. ? 2001 Microsoft Corporation. All rights reserved.

This happens because of the way row versions are checked (what was fetched
back to Access vs. what's currently in the SQL Server) when you try to
update a row, certain datatypes in the underlying SQL Server table can cause
the versions to appear different even if no one else changed the data.  This
can be fixed by adding a timestamp column to the SQL Server table that will
then be used for row version comparison.  KB article Q278696 explains one of
the situations that causes your problem.

--
Bob

------
Please do not send email directly to this alias. This alias is for newsgroup
purposes and is intended to prevent automated spam. I've been "encouraged"
to share this helpful information from our lawyers. This posting is provided
"AS IS" with no warranties, and confers no rights. You assume all risk for
your use. ? 2001 Microsoft Corporation. All rights reserved.

In most cases, the error message is caused by the database corruption. You
may take a look at these articles:

ACC97: How to Repair a Damaged Jet 3.5 Database               [accesskb]
ID: Q279334
http://support.microsoft.com/support/kb/articles/q279/3/34.asp

ACC97:  How to Troubleshoot Corruption in an Access Database  [accesskb]
ID: Q306829
http://support.microsoft.com/support/kb/articles/q306/8/29.asp

Hope this helps!

--- Simon Liao

Please reply only to the newsgroups. When posting, inclusion of SQL (CREATE
TABLE ..., INSERT ..., etc.) which can be cut and pasted into Query
Analyzer is appreciated.

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.  2001 Microsoft Corporation. All rights
reserved.