That's interesting, thanks, Troy. Razzak, please can you confirm if it is true?
I suppose it only makes a difference in multi-user mode but it sounds like a good idea to use browse first and then [F4] if you want to edit. Regards, Alastair. ----- Original Message ----- From: "Troy Sosamon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 19, 2002 5:54 PM Subject: RE: I/O Problems on SCONNECTed database > I think it does make a difference. > I think the EDIT all command is a leftover command from way back and the > Browse command is a newer command and works a bit differently. They both > look the same, but the Edit command pulls up your data set in edit mode > which means internally, R:base has got to keep track of the locks in the > database as you go through the rows of data. The Browse command is in read > only until you tell it you want to edit the data. I have made it a habbit > to always use Browse instead of Edit. > > Troy > > ===== Original Message from [EMAIL PROTECTED] at 9/18/02 4:10 pm > >Troy, > > > >Does it make any difference whether you edit or browse? Assuming no > >corruption, of course. > > > >Regards, > >Alastair. > > > > > > > >----- Original Message ----- > >From: "Troy Sosamon" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Wednesday, September 18, 2002 10:15 PM > >Subject: RE: I/O Problems on SCONNECTed database > > > > > >> Maybee a corrupted index. Rscope & autochk don't check indexes. > >> > >> You might want to try BROWSE instead of EDIT. That is a large table to be > >> editing. > >> > >> Troy Sosamon > >> > >> ===== Original Message from [EMAIL PROTECTED] at 9/18/02 12:45 pm > >> >I have two databases; for the sake of anonymity we'll call them A and B. > >> > > >> >A is the working database. B holds history and audits. > >> > > >> >A table 'audits' in B is SATTACHed to A. > >> > > >> >I have performed an unload/input on B. B passes all tests in R:Scope and > >> >AUTOCHK. > >> > > >> >If I do EDIT ALL FROM audits while connected to A and SCONNECTed to B, > >and > >> >then do [ctrl] [end] twice to go to the bottom of the table, I get "I/O > >> >error - check for a full disk." If I do "EDIT ALL FROM audits WHERE > >> >auddttm >= 091802" I get the same error. There are exactly two rows that > >> >meet the specification and they are the last two in the table. The field > >> >auddttm is not indexed. It is a datetime field. > >> > > >> >The table contains 106250 rows. > >> > > >> >Peforming the same actions on a table in B with only 28,643 rows works > >fine. > >> > > >> >The same actions while CONNECTed to B work fine. > >> > > >> >My TEMP directory is defined and scratch is set to write there; the disk > >> >containing that directory has 2.7 gb free. > >> > > >> >I get the same result using the R:Base ODBC driver and Oterro 2.5 > >1.850xRT03. > >> > > >> >I get the same result using R:Base version 6.5++ 1.855xRT03 and 6.5++ > >> >1.858xRT03. > >> > > >> >Any clues? > >> > > >> > > >> >Emmitt Dove > >> >Manager, DairyPak Business Systems > >> >Blue Ridge Paper Products, Inc. > >> >40 Lindeman Drive > >> >Trumbull, CT 06611 > >> >(203) 673-2231 > >> >[EMAIL PROTECTED] > >> >[EMAIL PROTECTED] > >> > > >> >================================================ > >> >TO SEE MESSAGE POSTING GUIDELINES: > >> >Send a plain text email to [EMAIL PROTECTED] > >> >In the message body, put just two words: INTRO rbase-l > >> >================================================ > >> >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> >In the message body, put just two words: UNSUBSCRIBE rbase-l > >> >================================================ > >> >TO SEARCH ARCHIVES: > >> >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > >> > >> ================================================ > >> TO SEE MESSAGE POSTING GUIDELINES: > >> Send a plain text email to [EMAIL PROTECTED] > >> In the message body, put just two words: INTRO rbase-l > >> ================================================ > >> TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >> In the message body, put just two words: UNSUBSCRIBE rbase-l > >> ================================================ > >> TO SEARCH ARCHIVES: > >> http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > >================================================ > >TO SEE MESSAGE POSTING GUIDELINES: > >Send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: INTRO rbase-l > >================================================ > >TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > >In the message body, put just two words: UNSUBSCRIBE rbase-l > >================================================ > >TO SEARCH ARCHIVES: > >http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
