On June 4, 2014 5:14:24 PM EDT, Joe Yoder <j...@wheypower.com> wrote: >The app is very basic as I have little experience with the design >environment. I don't think I'm doing buffering or transactions but if >one >of those is a default when one adds a grid to a form I might be. > >There is a free table, Inputs, which is the RecordSource >(RecordSourceType >1) for the grid. Inputs stores information about time based data >stored in >a second free table, Detail. The function of the app is to allow the >selection of one or more sets of time based data for reporting or >plotting. >The AdjRange procedure that gets called from the grid checkbox.valid >event >determines the range via "SELECT Min(BegStamp), MAX(EndStamp) FROM >Inputs >WHERE selected..." If the results are null the routine disables the >elements on the form that only make sense when something is selected. >When >the results are not null the values are written to the form Report >range >variables which are used as the earliest and latest calendar time that >can >be selected for output. The AdjRange procedure does not make any >changes >to the Inputs table at this time. In the future I want to have the >system >automatically allow only data that shares time stamps to be selected. >This >will probably involve adding a filter. > >I initially was writing the scan results to a cursor. I got suspicious >that maybe VFP was making invalid assumptions and reusing the results >of a >previous scan. I changed to writing to an array and things seem to be >working better. > >Typical sequence: > > - Nothing is selected in the grid and the controls disabled > - Clicking on a grid selection checkbox results in the controls come > alive with the correct data > - Clicking the same checkbox again and everything goes to sleep again > - Clicking another checkbox - the record is selected but the controls > stay sleeping > - Clicking yet another checkbox results in the controls waking up > - etc etc etc > >I tried adding a wait window before doing the scan thinking that a >manual >delay may give the system time to write to the table. This did not >make a >difference. At this point I'm thinking to try a non SQL scan to see if >that solves the problem. > >I hope this all makes sense. > >Thanks, > >Joe >
The checkbox click has not written to the table. I don't recall if the checkbox valid event has. You can try there. I remember a hack was to "go 0" in the event to get the update from a table. Though, grids do make things with tables interesting. -- Tracy _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/48cc1cf6-ed14-4126-a0a8-50b5aa2f9...@email.android.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
