Thanks, EMMITT.
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Emmitt Dove Sent: Tuesday, May 19, 2009 6:00 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: timer Jim, No problem with this. What's happening is the LABOR database is simply storing a table definition for the "remote" table. You can PACK/RELOAD etc. without issue. However, if you have multiple users, you don't want to be doing the SDETACH / SATTACH in your startup code. Just do the SATTACH once, and leave all of the SATTACH / SDETACH out of your .DAT. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of Jim Belisle Sent: Tuesday, May 19, 2009 6:02 PM To: RBASE-L Mailing List Subject: [RBASE-L] - timer Below is the DAT file I now use so a table from another RBASE database attaches. Everything is working fine. At the end of the day, though the SALES DB is detached, the table stays attached. My question is this: Since the Table never gets detached, will this prevent me from doing my maintenance on The LABOR DB (such as packing, etc). If yes, should I use a timer to detach the tables sometime at the end of the day? Or what would be the best way to care for this? Jim CONNECT Labor CLS SET ERROR MESSAGE 2038 OFF SDETACH Leadall NOCHECK SET ERROR MESSAGE 2038 ON SDISCONNECT ';Driver=R:BASE 7.6 Database Driver (*.rb1);dbq=Sales' SCONNECT ';Driver=R:BASE 7.6 Database Driver (*.rb1);dbq=Sales' SATTACH LEADALL USING LEADCODE ALIAS CONTACT,COMPNAME,COMPADD,COMPCITY,+ COMPSTATE,COMPZIP,COMPAREA,COMPPHPRE,COMPPHSUF,COMPEXT,sPROMOCAT,sPROMOI D,LEADDATE,+ DATEANSW,SALEPER,TICDATE,INTEREST,LEADGOOD,NOTES,LEADCODE EDIT USING KayParkMainMenu SDISCONNECT ';Driver=R:BASE 7.6 Database Driver (*.rb1);dbq=SALES' DISCONNECT EXIT RETURN
