In the past I have had intermittent problems with displaying tables and have thought that it was due to the size of the table - simply because it only ever seemed to happen with tables with large numbers of rows. Nothing specific although I think I did mention it here a while back. It also seems to have gone away of late but, perhaps, I'm just being more specific now with the number of rows I choose whereas I was not so careful when I first started using RBW.
However, I DO use a higher resolution screen - 1152x864 at the moment - to get the most information on screen as I can. I'm loathe to go back down at all but _maybe_ there is something to consider here. In order not to flood the list with replies perhaps only those who are using higher resolutions could indicate so and whether they, too, have had any unexplained "problems". At least it might put the possibility in or out of court. Regards, Alastair. ----- Original Message ----- From: "Ramsour Mike" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 03, 2002 7:30 PM Subject: RE: Table too big? -- Update > I modified the contents of my import file to make sure all fields are > zero-filled if no data exists in the original source data. The R:Base table > was purged of old data and the new data was loaded. R:Base still crashes if > I do a BROWSE * FROM CSR_TOL. I can do a SELECT * FROM CSR_TOL with no > problems. I can also do a BROWSE <col_list> FROM CSR_TOL and do not have > any problems. I can browse all records using a subset of columns. I tested > this using about 20 columns at a time. It's only when I BROWSE * FROM > CSR_TOL that the crash occurs. The crash only occurs if I try to browse all > columns when more than 40 records are selected -- which is essentially the > limit for the number of records that can be displayed in my browser at one > time. > > I have just narrowed the problem down to screen resolution. Up to this time > my monitor was set to 1024 X 768 resolution. On a whim I decided to change > the resolution to 800 X 600 -- and the problem no longer exists. At this > resolution I can now do a browse all and R:Base does not complain. It very > much appears to be a problem with the browser and screen resolution. Could > a video card have any effect on this? > > Insights anyone? > > Thanks -- Mike Ramsour > > -----Original Message----- > From: Sami Aaron [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 02, 2002 4:37 PM > To: [EMAIL PROTECTED] > Subject: Re: Table too big? -- Update - Razzak's Reply > > > > > > > Mike - > > Try your BROWSE with LAYOUT OFF/ON see if that makes any difference. If it > does, then delete the rows in SYS_LAYOUTS for this table. They could be > corrupted. > > Also - does it work if you SELECT * FROM table? > > Sami > ----------------------------------------------------------- > Sami Aaron > Software Management Specialists > 13214 W. 62nd Terr, #139 > Shawnee KS 66216 > 913-915-1971 > http://www.softwaremgmt.com > > > ----- Original Message ----- > From: "Ramsour Mike" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, January 02, 2002 2:56 PM > Subject: RE: Table too big? -- Update - Razzak's Reply > > > > I did an UNLOAD ALL and then ran the unload file to get a clean start. > > Still have the same problem. I can browse any group of records from this > > table as long is it does not exceed 40. I have another table that has > over > > 200 columns in it, 200 of which are double data types. When I do a BROWSE > > ALL from this table R:Base only displays 12 rows at a time, no crashes. > > > > In the problem table most of the columns use underscores in the names. I > > thought on the outside chance that this might be a problem I recreated a > > test table structured the same way except without the underscores, > reloaded > > the table and -- ended up with the same problem. > > > > Still searching. > > > > Thanks -- Mike Ramsour > > > > -----Original Message----- > > From: Troy Sosamon [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, January 02, 2002 3:24 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Table too big? -- Update - Razzak's Reply > > > > > > > > > > > > > > I would do it like this: > > > > >DISCONNECT > > >SET MULTI OFF > > >SET MESSAGES ON > > >SET ERR MESS ON > > set static off > > set error var er > > > > >CONNECT Concomp > > >RELOAD Boncomp > > >-- watch for any -ERRORS- > > > > if er <> 0 then > > -- errors occured during reload > > write 'Errors During reload - DID NOT COMPLETE' WHITE ON RED BLINK > > PAUSE 2 > > RETURN > > endif > > > > >DISC > > >DEL Concomp.RB? > > >REN Boncomp.RB? Concomp.RB? > > >SET MULTI ON > > >CONN Concomp > > >BROWSE TableName WHERE ... > > > > > > > Troy Sosamon > > > > > > ===== Original Message from [EMAIL PROTECTED] at 1/02/02 12:46 pm > > >At 02:34 PM 1/2/2002 -0500, Mike Ramsour wrote: > > >> > > >>Any other suggestions? > > > > > > > > >Mike, > > > > > >Make sure to RELOAD (not PACK) your database! > > > > > >Example: > > > > > >DISCONNECT > > >SET MULTI OFF > > >SET MESSAGES ON > > >SET ERR MESS ON > > >CONNECT Concomp > > >RELOAD Boncomp > > >-- watch for any -ERRORS- > > >DISC > > >DEL Concomp.RB? > > >REN Boncomp.RB? Concomp.RB? > > >SET MULTI ON > > >CONN Concomp > > >BROWSE TableName WHERE ... > > > > > >Have Fun! > > > > > >Very Best Regards, > > > > > >Razzak. > > > > > >===================================-============================ > > >R:BASE Developers's Conference: http://www.rbase.com/conference > > >Official R:BASE List Server: mailto:[EMAIL PROTECTED] > > >RBTI Events/Training: http://www.rbase2000.com/events > > >R:DCC Members: http://www.rbase2000.com/rdcc > > >================================================================ > > >R:BASE, Oterro & R:Tango are registered trademarks of RBTI. > > >==================================-============================= > > > > > >================================================ > > >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 > > > > > > > ================================================ > 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
