Iam creating a columnar report, 4 columns on the page.The columns are fine.
However,the client wants a vertical line running down the page between columns 1 and 2,2 and 3 and 3 and 4, like so: COLUMN1|COLUMN 2|COLUMN 3 |COLUMN 4 COLUMN1|COLUMN 2|COLUMN 3 |COLUMN 4 COLUMN1|COLUMN 2|COLUMN 3 |COLUMN 4 NOline on the far left or far right.Isthere a way to do this?I didn?t see any REPORT PROPERTY values inR:DOCS that would help.Have I missedone? DavidBlocker "David Blocker [email protected] Office: 781-344-1920 Cell: 339-206-0261" -----Original Message----- From: James Bentley [mailto:[email protected]] Sent: Monday, November 23, 2009 04:28 PM To: 'RBASE-L Mailing List' Subject: [RBASE-L] - Re: Large Tables & Indexes Chuck, Are the columns in the table in question all of fixed length or are there some variable length columns say with a NOTE datatype? Also, 9 indexes seem awfully high. What are you indexing? Perhaps if you post your CREATE TABLE and CREATE INDEXES and any appropriate ALTER TABLE statements we can get a better Idea of what is involved. Under version 8 my impression is that you should not have the problems you are experiencing. If the table definition is of all fixed length columns then an update to an existing row should not change the size of the RX2 file. Your symptoms seem to suggest that you have one or more NOTE datatype columns in that table definition. Jim Bentley American Celiac Society [email protected] tel: 1-504-737-3293 ------------------------------------------------------------ From: "[email protected]" <[email protected]> To: RBASE-L Mailing List <[email protected]> Sent: Mon, November 23, 2009 2:47:06 PM Subject: [RBASE-L] - Large Tables & Indexes Rbase 8.0.21.31001 We have a very large table three millionplus records and growing. We have indexes on 9 columns. The Database isabout 8 Gig. We do update processing that can easily touch 100 Krows with multiple columns. Via trail and error I learned that I must dropthe indexes on the updated rows or processing takes forever. After theprocessing I re-create the indexes. I have found that I need to packafter each Drop / Alter Table Add or the database gets to about 17 Gigwhere 8.0 seams to self destruct (I get Disk Errors and can't save thetable). Am I missing something. Is there a way to update large tableswithout dropping the indexes? Has anyone else experienced 8.0 'BlowingUp' at a little over 17 Gig? My indexes are all separate indexes. Whatwill happen to performance is I combine some of the indexes? Will itsave substantial space ?
