I have a few places in my code where I do two inserts into two different tables one right after the other. Most of the time that is not a problem. However there is code that runs on the thin clients out in the shop (hardwire) where recently the second table does not get populated as it should. Once again this is only once in awhile. The code runs in an on exit (from a field) EEP. The information going into both tables is from a view.
First insert INSERT INTO inventry + (list of columns) + SELECT list of columns + FROM twkinvtbl Second insert INSERT INTO workdetail + (list of columns) + SELECT list of columns + FROM twkinvtbl He form closes after dropping the temp view. Any BLUES CLUES? (Also this field is populated by scanning a location. All they user is supposed to do after the scan is hit the enter key.) James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/CH2PR02MB704775C028C7BDA1866388B6A0EB0%40CH2PR02MB7047.namprd02.prod.outlook.com.
