I'm with Dennis here. I rarely use DB Grids or Scrolling Regions anymore
-----Original Message----- From: Dennis McGrath <[email protected]> To: [email protected] (RBASE-L Mailing List) Date: Thu, 1 Dec 2011 15:07:26 -0600 Subject: [RBASE-L] - RE: I/O problems - Check for a full disk I personally prefer using a variable lookup listview to display the data in this scenario. The listview lookup can be changed on the fly. Or use variables in the lookup where clause and changing the variables reloads the listview display right away. Dennis McGrath Software Developer QMI Security Solutions 1661 Glenlake Ave ItascaIL 60143 630-980-8461 [email protected] From:[email protected] [mailto:[email protected]] On Behalf OfTom Frederick Sent: Thursday, December 01, 2011 2:55 PM To: RBASE-L Mailing List Subject: [RBASE-L] - I/O problems - Check for a full disk I commonly use DB-Grids in lower half of forms as summaries and full fields in the top half for editing. Works great. Got a form which creates temp table (tGoals), loads the DB-Grid, and allows users to update progress on the goals. Several buttons allow the user to drop, then rebuild the temp tables using PROJECT and some variable criteria such as a date. DB-Grid gets refreshed with the new tGoals through PROPERTY commands. That limits the number of rows a user sees. Edits to the temp table get immediately UPDATED to the master table. This works at startup and first rebuild. Second tGoals rebuild consistently gets ‘I/O problem-check for a full disk’. Database is 9.1 64 with latest updates and rebuild is clean. I can do what I want by using only the master table, but the users get lost with too many rows. Is there some way to set a criteria within a DB-Grid or extended DB-Grid to limit what rows are used or are these simply the wrong options to use? Tom Frederick President/CEO ElmCity Center 1314 W Walnut Jacksonville, IL 62650 W- 217-245-9504 F - 217-245-2350 E - [email protected]
