Oma 1. I ROUTINELY make a PACK KEYS command part of my daily backups for clients, for two reasons: a. In case of index corruption such as you're expeiencing b. Becuase R:Base recalculates important data distribution statistics during this routine which will improve speed of queries and all WHERE clauses.
2. If this is happening regularly, have you tried these commands? (I;m assuming this is the DOS app you've been wrtiing about). They make more buffer space avaialble for indexing and data maniuplation: SET VAR MICRORIM_F2MAXBLK=128 SET VAR MICRORIM_F3MAXBLK=128 David Blocker [EMAIL PROTECTED] 781-784-1919 Fax: 781-784-1860 Cell: 339-206-0261 ----- Original Message ----- From: "Office" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Friday, December 05, 2003 12:13 PM Subject: [RBASE-L] - No. 3 File Corruption (Index File) > Just wondering what others have done to address this issue! > No. 3 File Length error! > I have a network application that has had this problem every few months. > When the client starts the application rbase will not start. > When accessing the client's DB via the R prompt. I can run autochk and > it tells me that the no. 3 file has an incorrect file length. If I > attempt to use(edit,entry,design,copy,rename,delete) a form or a report > Rbase closes. > I then run Rscope on the DB and it comes back with no errors. > I then open the database via the R prompt and unload and reload. The > error is corrected. > Or I pack keys and the error is corrected. > > During the client's backup and administration routines that run every > morning at 2AM. I unload the DB before doing the administrative task and > packing the database. After these are done I do another unload. But I > do not reload the DB. > > The scratch file is set to c:\temp. But I sometimes see $$$ files in > the DB folder. > The client expreniences a slow down before this happens. When at the > main menu (form with buttons) they attempt to run something then Rbase > closes without error message and if they attempt to run rbase again it > doesn't not start. > > I've written a routine to address this issue (using packing of keys) for > the client to run when this file get out of wack and Rbase will not run. > > The client's network uses VPN connections using Terminal services to > access the DB from remote locations (3 total). > The DB size is only 120MB. The VPN connections are use only for looking > up information no data gets edited or entered. Editing and entry of > data occures only with in the local network. The network cards are all > Intel 1Gbit, Linksys 1Gbit Switch, Sonicwall SOHO3 router(everything > here seams to be working ok). > > Those who have had this issue before, what have you done to address this > issue? Is it settings in the OS or Rbase? Or is it something that can > happen with this type of access method (using terminal services)? Let > me know your experiences with this issue! Any and all would be > appriecated. I just want to get a better understanding of how this > could be happening! > > Have a great weekend! > > Oma > >
