Marc,
The size of your RX1 is not an issue. File 1 stores the table definitions, that's all. It is larger since there is more physical space devoted to the information stored there. The RX3 stores the index data. Since V8 operates with 64-bit addresses, this file will also naturally be larger. Emmitt Dove Manager, Converting Applications Development Evergreen Packaging, Inc. [email protected] (203) 214-5683 m (203) 643-8022 o (203) 643-8086 f [email protected] From: [email protected] [mailto:[email protected]] On Behalf Of MDRD Sent: Tuesday, May 05, 2009 12:41 PM To: RBASE-L Mailing List Subject: [RBASE-L] - Re: 7.5 vs V8 speed I just did a Unload all and deleted all Report expressions with a Where clause and it is still slower than 7.5 but getting closer. Since I converted to V8 my #1 file is about 4x larger and #3 file 2x larger Could that be a problem? At this point I guess I will just have to test different things and hope I find the answer. Thanks Marc From: Bill <mailto:[email protected]> Downall Sent: Tuesday, May 05, 2009 11:07 AM To: RBASE-L <mailto:[email protected]> Mailing List Subject: [RBASE-L] - Re: 7.5 vs V8 speed Marc, Is a simple "Select" with that where clause faster than a report generation? If so, check what Larry suggested (lookups), and also check "pass settings" to see if it is set to 2 passes, and if that can be changed to single pass. If the SELECT from the view is fast, and the report is slower, then just PROJECT TEMP tablename FROM VIEWNAME WHERE .... and print from a new version of the report -- copied from the original -- but which uses the temp tablename instead of the viewname. If the SELECT is slow, too, then you need to work on the view definition. Bill On Tue, May 5, 2009 at 12:01 PM, MDRD <[email protected]> wrote: Larry They are Indexed. Marc From: Lawrence Lustig <mailto:[email protected]> Sent: Tuesday, May 05, 2009 10:43 AM To: RBASE-L Mailing List <mailto:[email protected]> Subject: [RBASE-L] - Re: 7.5 vs V8 speed << This view is complex at least for me but I am not sure that is the major snag, Doing Browse all from the view using the same Where clause is 1/4 the time to Print the report. >> Check all look-ups in the report and see if one of them is missing an index. -- Larry
