> Could you explain a little more. Larry is running into what I think you are > talking about. In the VFP world I'd call that a "Dangling" referrence that > caused the program to think there was still a variable/reference that needed > to be released. >
From my experience, this is what is happening: When you browse a dataset, the data is copied from the dataset to the correspondent field (dTextBox, dComboBox, etc etc) until it end updating all the fields in the form.... The problem arises when there is an exception in this process, you end up with data from 2 records mixed up, wich may of course cause problems. My previous commit was an attempt to isolate the problem to the field causing the problem (a combobox for example wthout the correspondant key to the one in the current record), the form would load all the remaining fields (my commit didn't do it..but maybe we could reset the value of that field using resetChoices()) I'm not familiar with VFP so i don't know if it is simillar, but i guess not... Of course the REAL question is: Why isn't there the correspondent key in the combobox, the problem is obviously in the data, maybe some missing validation, however this default behaviour is also dangerous in my opinion, but i admit my solution was far from perfect... I'll give it some extra tought...and discuss it here Pedro _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
