MS Access Write Conflict error

[suzieh246]

I have an MSAccess 2003 SP3 front-end linked to a SQL back-end.
I am getting a write conflict on a form but am not writing back to SQL at this point as I am using temp tables solely. I get the write conflict error after updates are made to the forms (there are main and sub forms). I do not get this error at the point of writing back to the Sql tables. I get it after updates are made to the TEMP tables which are MSAccess.
There are bit fields in the Temp tables. If I change the Temp table bit fields to 0 default value, will this cure the problem.
I have seen posts that say I need to modify the SQL tables but again how could this help if I am using Access Temp tables at this pint?
Thanks.

 

[SkipVought]

Hi,

Welcome to Tek-Tips.

You will get much better responses, if you post your MA Access questions in MS Access forums, of which there are many. Try Forum702 or Forum181, for instance.

Skip,
^{Don't let the Diatribe...
talk you to death!}
_{Just traded in my old subtlety...
for a NUANCE!}

 

[dhookom]

If you haven't posted elsewhere yet, I would change any bit fields to int or tinyit. IMO, bit fields are close to worthless. Make sure you have a default specified if you do use bit fields.

Duane
Hook'D on Access
MS Access MVP