Saving Current Record On Form - Access 2007

[Jeff Garrison]

All -

I ran into something today that is going to kill me if I don't figure it
out. I'm working on a db that uses Access 07 as the front end and SQL as
the backend. Here's my problem...

When I'm in a form and make a change, if I fire off saving the record as an
After Update Event or even changing a field on the form and closing out, I
get the dreaded "Write Conflict....This record has been changed by another
user since you started editing it...." I'm trying to save the record before
I go any further, but still get the same message. No one else is in the
database that could lock the record, so I'm at a loss. The wierd thing is
that it was working fine up until mid morning. Ever since, I've been
pulling out my hair (what's left of it) trying to figure this out. I even
uninstalled Office 07 and reinstalled it. Another funny thing is that I
have an 03 frontend that works fine.

Any help would be much appreciated.

Thanks.

JeffG

 

[Tammy F]

I get a write error if I have any NULL values in the records in a Yes/No
field on the Server. I set those to no and I can write to the record again
from Access.
Tammy

 

[Albert D. Kallal]

When I'm in a form and make a change, if I fire off saving the record as
an After Update Event or even changing a field on the form and closing
out, I get the dreaded "Write Conflict

When you ay "fire off saving" you might want to expand on what you mean by
that term...

Can you regular edit the form, and simply close, or navagate to the next
reocrd, and everything saves just fine???

If the above is your case, and I suspect you executing or running some code
that modifies the actual record set behind the scenes (behind the form), and
not the actual data in the form. The way to solve this is to ensure that you
force a disk write in your form code *before* you execute any of that code
that does an update on possibly the same data.

To force the describing your forms code, simply go

if me.dirty = true then
me.dirty = false
end if

... you code that does update of data goes here....

 

[Jeff Garrison]

Actually, I figure out the problem...somewhere along the line, the table go
corrupted. I exported the SQL table, deleted it, and re-imported it and all
works fine.