I have an DBGrid bound to a Data Control, along with several TextBoxes
bound to the same Data Control. I use the DBGrid as a list box, with the
record selectors disabled. A person select whatever record by clicking
on rows in the DBGrid.
My problem is that a field value in one record may get written into
other records by mistake, screwing them up. I could solve this by using
unbound TextBoxes, a recordset object, and seek instructions, then
stuffing their values by using the Data Control's Reposition event. I
then have to monkey with LostFocus and DataChanged properties on the
TextBoxes, which is a pain.
I think because I have two controls bound to each field it gets out of
sync, though editing in the DBGrid is disabled. Is having my TextBoxes
unbound the only alternative? Has anyone experienced similar problems?
This is a VB 5.0 app. I had a similar problem with Access, and mostly
use unbound TextBoxes with Access as a result. Unbound controls are much
easier to manage in Access however. Thanks