Wish mine was that easy. Something happened overnight on Jan 10 that has brought the database to it's knees. I can only have one at a time in if they want to get anything done. AUTOCHK shows everything is fine. The database is reloaded everynight. So I know it's not an R:BASE thing.
File transfer across the network is fine. It's like something is watchdogging the RX files. I don't have antivirus running. I'm kinda at a loss. Jan -----Original Message----- From: [email protected] To: [email protected] (RBASE-L Mailing List) Date: Wed, 19 Jan 2011 20:33:19 +0000 (UTC) Subject: [RBASE-L] - Re: Pack versus Unload/Load Thanks all. That is what I needed to know. I know the UNLOAD/LOAD the preferred method, but I needed to know about the PACK as there are times that a full unload/load is difficult to fit in. (Not that I am having any serious problem. 6 years on a production database with 10 wireless units on fork trucks, several "unschooled users" , 300,000 sqft facility with ethernet wiring running who knows where and not a single corruption until today! A quick 2 minute PACK got us back and running, but I wanted to check about it anyway.) A good load/unload will wait until tonight Thanks again. -Bob ----- Original Message ----- From: "Lawrence Lustig" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Wednesday, January 19, 2011 1:46:08 PM Subject: [RBASE-L] - Re: Pack versus Unload/Load << Will the PACK command fix anything that a Load/Unload would fix? At least in theory? >> No. With PACK you don't get a new copy of the RB1 file so problems in the database structure (like mismatched PK/FK relationships) will carry over. -- Larry
