Hi Mike- I ran into a similar problem where I created a table with 12 note fields, and experienced data loss. Each line of a table is limited to 2000 bytes of data. Exceeding that ultimate length may be your issue.
Lee Bailey Bailey & Associates E-Mail: [EMAIL PROTECTED] Phone: 954-659-1780 Fax: 954-659-1781 ----- Original Message ----- From: "Michael Young" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 02, 2002 1:28 PM Subject: Re: Table too big? > Hi Mike, > > I would look at your input file. Is it formatted correctly? Are > there control characters in it? You could also try a BROWSE ALL > FROM CSR_TOL WHERE COUNT = 1 and see if that works. It is > probably hitting something weird at one of the rows. Change the > where clause to WHERE LIMIT = 10 or 100 and see where you can > go with it. That might give you an idea where the problem lies > in the ASCII file. I think R:Base can have around 4096 > characters in a row of data. > > If the original table the data comes from is an R:Base table > then look at the data in that database and see if you can find > anything strange. I have sometimes found that one row of messed > up data can cause all sorts of problems. If you dump that row > then things get back to normal. > > Good luck, > Mike Young > > On Wed, 2 Jan 2002 13:12:15 -0500, Ramsour Mike wrote: > > >I created a new table that has 91 columns in it distributed this way: > > > >Type # of columns > > <<...OLE_Obj...>> > > > >I load the table from an ASCII fixed field file with 435 characters per > >record. R:Base loads the table properly, etc. When I try to do a BROWSE * > >FROM CSR_TOL R:Base crashes every time. The database that I originally > >created the table in is fairly large, RB2 > 770 MB and RB3 almost 200 MB so > >I thought I might be reaching some limitation there. I then created a new > >database with just this new table in it. I ended up getting the same > >result. Each time I do a BROWSE * FROM CSR_TOL R:Base crashes. I can limit > >the number of columns that I browse and R:Base doesn't seem to mind. It's > >just when I browse all columns. > > > >I am using the latest version of R:Base 1.850xRT03. Is the table too large > >as in too wide for the amount of data per record, is the indicative of a > >data corruption problem or should I look somewhere else for an answer. > > > >Thanks for any and all input. > > > >Mike Ramsour > > > >================================================ > >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 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 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
