Write conflict

[IslandHydro]

Hello All,



I'm brand new to this forum, so please be gentle if I'm asking a dumb question . I have a large access database (access 2010) where I often need to programmatically modify values for fields on the current form. I've tried modifying the control on the form directly through code, and this works but often triggers a write conflict error (another user has modified) when I move off the record. I think I've also tried update queries (modifying the underlying dataset directly rather than through the form). Worse than the error message, if I choose to overwrite it appears to corrupt the database! What's the right way to do this?

Thanks,
Doug

[ItsMe]

How does the DB appear to be corrupt? If you overwrite another user's changes, that record will be saved exactly like it looks on your current form.

Perhaps overwriting another user's changes is breaking referential integrity rules. Is it really another user or do you have two forms open?

[Missinglinq]

Is this being used in a multi-user environment? If the answer is yes, is it split into a Front End/Back End configuration, with each user having a copy of the Front End on their hard drive?

Linq ;0)>

[IslandHydro]

How does the DB appear to be corrupt? If you overwrite another user's changes, that record will be saved exactly like it looks on your current form.

Perhaps overwriting another user's changes is breaking referential integrity rules. Is it really another user or do you have two forms open?

It is actually corrupt, in that data in fields that should be legible strings becomes gobbledeegook (that is the technical term) that looks like machine language code viewed in a text editor. When this happens I just have to go back and use a backup copy cause the database is screwed.

[IslandHydro]

Is this being used in a multi-user environment? If the answer is yes, is it split into a Front End/Back End configuration, with each user having a copy of the Front End on their hard drive?

Linq ;0)>

It is not really a multi-user environment although I do have it broken into a front and back end. There is one computer that keeps the live copy of the database, everyone else looks at a copy on their own local machine. The corruption seems to occur when I get the write conflict (another user has modified) error and I choose save.