On 7/2/07, Lew <[EMAIL PROTECTED]> wrote: > > The next situation he addresses is one in which the same and linked data > appears & must be refreshed & > editable on more than one screen, so in order for changes to be visible, a > commit must be issued leaving him > without the option of a rollback.
I would resist that as far as possible. It violates data integrity. I've coded around this kind of problem in a couple of ways: you could share the same private data session between forms, so they each see the same buffered data, or you could have a set of "pending transaction" tables that hold the data that will be committed if the entire multiple-screen process completes, or gets purged if the process is cancelled/rolled back. -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
