Thursday, July 23. 2009
Write Conflict Where None Exists
I recently encountered the following message in Microsoft Access 2003 when attempting to update any column of a linked table (linked to an MSSQL2005 DB):
The interesting part of this story is that there really shouldn't be a write conflict in the data because the linked table in question is in a DB on my local computer which is only being accessed by Access and has no triggers which could be confusing Access. Further investigation, and a useful thread on Bytes, revealed that the problem was columns in the linked table which have the datatype
Write Conflict
This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made.
BIT
and was allowed to be NULL
. Changing the columns to BIT NOT NULL
and refreshing the linked table in Access solved the problem.
Update: KB 280730 covers this issue.
LinkMasterFields Error about missing Automation object
I recently encountered the following error message in Microsoft Access 2003:
The LinkMasterFields property setting has produced this error: 'The object doesn't contain the Automation object 'Tablename.''
After further investigation, as suggested by a thread on microsoft.public.access.forms, the problem appears to be related to duplicate columns in the form Record Source. However, the error is not limited to simple duplicate columns. In my case, the duplicate name was the result of a table join where the compound names were distinct (i.e. Table1.Col1 and Table2.Col1), but the simple column names were not, which resulted in the error. Perhaps I shouldn't be using joined tables as my Record Source... perhaps.
(Page 1 of 1, totaling 2 entries)