You mean to say that in your first post you fogot to mentoin that you are
using sql server?
You don't think that was a important detal? You should also menton what
version of sql server.
When using sql server (or oracle, or sybase, or MySql), ms-access has to
"figure" out if hte reocrd has been changed. If you don't have a primary
key, and a timestamp field expsoed, then it makes things VERY difficlt for
ms-access to determine if the record has changed. In fact, when using
oracle, or (in your case, sql server), then I find sub-forms OFTEN do not
function correct untill you include a timestamp field in the sub-form.
Of course, if you not using sql server, then none of above advice about
timestamp fields applies, and you don't need them.
If you are not actually using sql server, then that kb aritcle (if you read
it) does not apply.
It would be *quite* surprising that just convering from a97 to a2003 would
cause that problem to rear its ugly head. 99% of the time (when not talking
about sql server), that write conflict probem is due to you running code, or
launch antoher form that mdoifyes the CURRENT data on the CURRENT form, and
that form has PENDING data. (that means, you run some code, or do somting in
code that mdoifyes the CURRENT reocd, but you do so with a reocordset, or
udpate query, or even luanch antoher form. (however, this problem would
normally NOT change due to upgradin to a2003).
If you ahve any code that creaes a new reocrdset, runs a udpate query, or
launchaas antoher form, you need to force a disk write of the current forms
data BEFORE you run this code.
go:
if me.dirty = True then
me.dirty = false
end if
....... your update code goes here (or code to launch other form..or
whatever)
I would double double double check your original code, and if we are NOT
talking about sql server, then the above is likely your problem (but,
strange that it did not exist in a97). and, if in fact you are talking about
sql server, then make sure a pk + timestamp field is exposed.
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com