what does 'inconsistent updates' really mean?

[Guest]

I have a form that will be used by 20 users. It has about 50 controls. In
order to produce the correct criteria, I need to base it on a query of a
query (can't find any other way to get correct criteria).

The data becomes updateable if I turn on 'inconsistent updates' but this
terminology worries me because so many people will be updating this data.
Does turning this on increase the risk of data collision or corruption?

I can't seem to find much info on what that feature really means (either in
Help or other discussion threads).

Thanks much,

 

[Michel Walsh]

Hi,

That enters in consideration if you have a relationship one-to-many.

That won't change anything if you have enforced a relation and allow to
cascade updates, both consistent and inconsistent produce, in that case, the
same effect (see below).

If you only enforce the data relationship, a consistent update allows you
to only update the many side, while an inconsistent update will allow you to
update the "one" side of the relation, which may break the data integrity
relation.

If the Cascade update is defined, the modification of the "one" side will be
cascaded to the "many" side, automatically.



Hoping it may help,
Vanderghast, Access MVP