LeanneGodney
Technical User
Hi there,
I'm having quite a big issue with my ADP at the moment. I have a disconnected recordset that is created when the form opens. The form's recordset is set to the disconnected recordset.
The user starts adding a new record. For my date fields I don't allow manual entry because of different date formats, so the user has to double click the field to get a calendar control. They choose the date they're interested in.
When they click ok my code tries to write the new date to the disconnected recordset's current record. The fact that it's a date is irrelevant. Trouble is that the disconnected recordset has not recognised that a new record has been added yet! So I get a BOF/EOF error. Even though the form has a newly created unsaved record!
I have tried forcing the form to save when the user double clicks, but this saves the record in the form without it registering in the disconnected recordset!
I'm sure you can understand my frustration.
Why does an ADP disconnected recordset (ADODB) SOMETIMES recognise that a new record has been added, and sometimes not?
Does anyone know how to fix this? I've created a silly fix that clones the disconnected recordset, empties the disconnected recordset and then set it back to the clone. This works, but I don't like it.
Can anyone shed some light on the subject??
Thanks,
Leanne
I'm having quite a big issue with my ADP at the moment. I have a disconnected recordset that is created when the form opens. The form's recordset is set to the disconnected recordset.
The user starts adding a new record. For my date fields I don't allow manual entry because of different date formats, so the user has to double click the field to get a calendar control. They choose the date they're interested in.
When they click ok my code tries to write the new date to the disconnected recordset's current record. The fact that it's a date is irrelevant. Trouble is that the disconnected recordset has not recognised that a new record has been added yet! So I get a BOF/EOF error. Even though the form has a newly created unsaved record!
I have tried forcing the form to save when the user double clicks, but this saves the record in the form without it registering in the disconnected recordset!
I'm sure you can understand my frustration.
Why does an ADP disconnected recordset (ADODB) SOMETIMES recognise that a new record has been added, and sometimes not?
Does anyone know how to fix this? I've created a silly fix that clones the disconnected recordset, empties the disconnected recordset and then set it back to the clone. This works, but I don't like it.
Can anyone shed some light on the subject??
Thanks,
Leanne