This procedure is used once or twice a month. On the day that it does get used it can be run multiple times that day with the procedure taking at least a few minutes to complete. The procedure can only be ran by a single user at a time
The procedure updates a table that is indexed on a keyfield + our own date/time stamp (char 20) Our date/time stamp is just SYS(11,DATE())+"-"+ALLTRIM(STR(SECONDS())) A record only needs to get added to the table once for each keyfield per update. * at beginning of procedure init stamp varible for this update UpdStamp = SYS(11,DATE())+"-"+ALLTRIM(STR(SECONDS())) . . . * where we update the table IF !SEEK(keyfield + UpdStamp) * must be new update APPEND BLANK REPLACE stamp WITH UpdStamp ENDIF REPLACE field1 WITH var1, REPLACE field2 WITH var2... Not sure why SYS(11,DATE())+"-"+ALLTRIM(STR(SECONDS())) was used for the date/time stamp as opposed to something like TTOC(DATETIME(),1) I think the code is fine, although not optimized as much as it could be and dont want to change the code unless necessary. This code has been in place for a while now and has worked fine so far. Does anyone seen any other problems with it? Thanks, kc _______________________________________________ Post Messages to: [email protected] 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.
