Bill - Trust me, the MDI forms can really dazzle - they can have them all open at the same time, move them around on the screen, etc.
It's a little more work to set it up - but you can just copy/past the objects from your current tabbed form so you don't really have to re-create the individual forms again from scratch. Sami -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Eyring Sent: Monday, August 04, 2008 4:12 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: DBGrid Question Sami Thanks for the option. I had wanted to use a multi-tab form to get away from individual forms which I used in 6.5++. I wanted to dazzle using the latest features of 7.6. I originally had scrolling regions where the dbgrids are now and it was even slower than the dbgrids. Perhaps scrolling regions or dbgrids are not meant to be in multi-tab forms ? Bill -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Sami Aaron Sent: Monday, August 04, 2008 4:21 PM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: DBGrid Question Bill - I switched some forms with multiple tabs/tables to be MDI forms and found that they are really fast. I created a control form where the user clicks a button and it opens the appropriate MDI form with the proper sort order and no overhead of multiple tables or the "ARRANGE" clause. Sami ____________________________ Sami Aaron Software Management Specialists 913-915-1971 [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Eyring Sent: Monday, August 04, 2008 2:41 PM To: RBASE-L Mailing List Subject: [RBASE-L] - DBGrid Question I have an 8 tab form used for editing data. On 6 of these tabs I have a dbgrid. For the tabs with a dbgrid, If I use a dbnavigator arrow or click on succeeding rows the response time is much slower than if these tabs were standalone forms. The command I use to start this form is; EDIT USING Book2 + TABLE=BOOKS PRIMARY KEY FIELD=DEALNO ARRANGE other BY dealno, + TABLE=OTHER FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE advances BY AdvRdate desc, + TABLE=ADVANCES FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE paydeal BY PDpayshare, + TABLE=PAYDEAL FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE rledger BY dealno,RLtrandate desc, + TABLE=RLEDGER FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE clroyalties BY dealno, + TABLE=CLROYALTIES FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE clsubrights BY dealno,SRRSdesc, + TABLE=CLSUBRIGHTS FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO ARRANGE royrec BY dealno,rrtrandate desc,rrroyalty + TABLE=ROYREC FIELD=DEALNO IS A FOREIGN KEY TO BOOKS COLUMN=DEALNO whe cno=.vcno and dealno=.vdealno I confirmed that all of the tables have different column names except for the primary and foreign key. I am using the latest 7.6 update 7.6.4.30728. Can anyone point me in a direction where I can speed things up in these dbgrids ? Thanks in advance. Bill Eyring
