John, Even with 6.5, you are not approaching any limits nor the number of records that would cause speed issues. (There are SystemV installs still running today that have hundreds of thousands of records without speed issues.)
Make a backup and UNLOAD / RELOAD your database. That will reclaim (compact) any phsyical disk space spread throughout your database and it will recreate you indexes. This can make a significant difference. A PACK command can do similar, but make sure you have a back up and plenty of hard drive space. Then you should look at your indexes you have applied. For instance, applying an index to a column that has only 2 unique values over 35,000 records does not do much good. Having indexes on too many columns (I have seen cases where people put indexes on all columns) will actually cause the system to run slower. Views can be very much effected by proper indexing. You can rest assured that in your case it is not the number of tables or records causing a speed issue. -Bob -- Thompson Technology Consultants LaPorte, IN 46350 219-363-7441 -------------- Original message -------------- From: "John Croson" <[EMAIL PROTECTED]> > Unfortunately, I'm using 6.5+. > > On Fri, Jul 18, 2008 at 3:04 AM, A. Razzak Memon wrote: > > At 03:06 PM 7/17/2008, John Croson wrote: > > > >> Is there a maximum record / table count for RBase? > > > > John, > > > > Here's a comprehensive chart to explain it all. > > > > http://www.rbase.com/products/compare.php > > > > Very Best R:egards, > > > > Razzak. > > > > > > > > > > -- > John Croson > [EMAIL PROTECTED] > http://pcnorb.blogspot.com/ > http://pcnorb.homelinux.org/ > >
