P
Paul
Hi
Can anyone tell me if the following is a confirmed bug?
I have a subform which is set to 'continuous form'. Each control has a
function for its double click event. In the function I capture the primary
key of the record that has been double clicked and use it to build a filter
for another form with code such as...
strFilter = "[" & form.recordset.fields(0).name & "] = " &
form.recordset.fields(0).value
This works perfectly unless I double click on record X, then move back to
the subform and double click on record X again without having moved to
another record first.
Although form.currentrecord and the like yield results,
form.recordset.fields(0).value yields 'no current record'.
I have implemented a workaround (get the value from a hidden control rather
than the recordset), but this doesn't appear to be 'correct behaviour' -
some parts of Access know what record is currently selected and other parts
do not.
TIA
Paul
Can anyone tell me if the following is a confirmed bug?
I have a subform which is set to 'continuous form'. Each control has a
function for its double click event. In the function I capture the primary
key of the record that has been double clicked and use it to build a filter
for another form with code such as...
strFilter = "[" & form.recordset.fields(0).name & "] = " &
form.recordset.fields(0).value
This works perfectly unless I double click on record X, then move back to
the subform and double click on record X again without having moved to
another record first.
Although form.currentrecord and the like yield results,
form.recordset.fields(0).value yields 'no current record'.
I have implemented a workaround (get the value from a hidden control rather
than the recordset), but this doesn't appear to be 'correct behaviour' -
some parts of Access know what record is currently selected and other parts
do not.
TIA
Paul