> Barney, thanks for your advice. I understand your suggested
> solution for the simple example I wrote here. But my main concern
> in practice is that any field in any table could change. So for an
> application where all information submitted by the original submiter
> is complete, the reviewer could now start the review process by
> editing the contact info first. Because of reviewer has not
> reviewed any application-level data yet, how would I tie the new
> inserted contact record back to the application table if I start out
> by inserting a new contact record?
Can you provide a (small) example of a schema as you would use it
without multi-versioning, that would give a problem when using
multi-versioning?
Jochem
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
