Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.paradox    |    To crash or not to crash, asks Borland    |    9,834 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 8,418 of 9,834    |
|    Jim Moseley to All    |
|    Re: Unlocking problem...    |
|    04 Apr 07 12:09:31    |
      From: jmose@mapson.attglobal.net              Kenneth,              I can see how you'd get at least one 'not in edit mode' error, but without       seeing all of your code I can't say what else is wrong.              When you open a form, it will automatically go to the first row in the table       (based on the data model, filters, etc.). It seems like you will always       try to flag this row as Viewed=today(), which I don't think you want.              A form doesn't automatically open in Edit() mode either, so it will arrive       on the row before you can issue the Edit() command, causing the error.              Rather than using dataArriveRecord, is there a common place in your code       where you control which row is displayed on the screen? If so, that is       probably       the place for Viewed=today().              If you still want to use dataArriveRecord, then set a global switch once       you've settled onto a 'good' row, and only do the update if it is set. You       can set the switch to false at the beginning of the form's init() method       (before doDefault), then set it to true once you qLocate (or whatever) your       first row.              Also, check your code for EndEdit() or CancelEdit() and either turn off the       switch, or toggle edit() back on just for the Viewed=today() update.              HTH,       Jim Moseley              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca