G
Greg Crowe
I am running into a write conflict that has me really stumped.
My situation: Access 2003 on XP clients. Main form, with tab control
containing SubForms. Main form is bound to a single SQL table (linked
tables). Subform is bound to a simple inner join (1:1) of two SQL linked
tables.
I can update *every* field on the SubForms except one. The field in SQL is
just varchar (500). It has never been a problem until my most recent build
of this project. According to my change log, I have not touched this
particular portion of my project for some time (several public builds) so it
is interesting that this is happening now.
Any time I modify this one field and save, I get the Access write conflict
error.
- I am sure nobody else is using the data (I'm developing in a mirror of our
production SQL environment and I'm the only developer on this box).
- I have relinked access to SQL.
- Updating the field in question does not fire off any VBA code.
- There are no macros.
I am really at my wit's end here and running out of ideas as to what this
could be. Can anyone help?
- Greg Crowe
My situation: Access 2003 on XP clients. Main form, with tab control
containing SubForms. Main form is bound to a single SQL table (linked
tables). Subform is bound to a simple inner join (1:1) of two SQL linked
tables.
I can update *every* field on the SubForms except one. The field in SQL is
just varchar (500). It has never been a problem until my most recent build
of this project. According to my change log, I have not touched this
particular portion of my project for some time (several public builds) so it
is interesting that this is happening now.
Any time I modify this one field and save, I get the Access write conflict
error.
- I am sure nobody else is using the data (I'm developing in a mirror of our
production SQL environment and I'm the only developer on this box).
- I have relinked access to SQL.
- Updating the field in question does not fire off any VBA code.
- There are no macros.
I am really at my wit's end here and running out of ideas as to what this
could be. Can anyone help?
- Greg Crowe