Bet I know what the problem is.... When you do a refresh are you deleting rows from the temp table? That often corrupts temp tables, just had that happen to me today when writing a new program. Drop and recreate your temp table rather than deleting rows.
Karen In a message dated 12/1/2011 3:08:35 PM Central Standard Time, [email protected] writes: > 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? > > > >
