Rob, I had a similar occurance on a form. I fixed it by defining an pushbutton that took you to the next and previous row with no update, and then next and previous with an update. The next was just the standard pre defined command file with a pushbutton, the updates were :
set var vEDate = .#date update Tablename set edflag = .vEDate where ssno = .vssno Nextrow Return SSNo is an autonumber column that I use to track all of the rows in the table, so it makes it easier to track. The same thing could be done with a scrollable cursor, and an update where current of CursorName. I'm not sure if this will work on a region, but it works on individual rows on a form. I hope it helps. Damon D. Kaufman President Stalder Spring Works, Inc ISO-9002 / QS-9000 Certified 2345 S. Yellow Springs St. Springfield, Ohio 45506 Voice 937-322-6120 Fax 937-322-2126 email: [EMAIL PROTECTED] In a message dated 2/13/2002 5:58:36 PM Eastern Standard Time, [EMAIL PROTECTED] writes: << Initially, the focus is on the transactions. If they click back to the top (Customer Side) and make a change how can I detect a change to that specific table and update the DateTime stamp? I've experimented with the following technics without success: - Triggers (too constrictive in forms with regions) - Variables in Form (get evaluated regardless of change to data) - Using an EEP on Entry/Exit to table <or> after Leaving Section (Form_Dirty_Flag detects changes made to ANY table) >> ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
