Delete should not cause this behavior (and it doesn't for me using the
RB database engine). Inserting new records does close the cursor,
which I believe is described in the docs, so you will no longer have
access to any of the rows. You can get around this by running the
query again and moving to the end. Try putting this code in whatever
button you have that is actually doing the Insert:
DataControl1.RunQuery
DataControl1.MoveLast
-- Paul Lefebvre
On Sunday, March 30, 2003, at 08:03 PM, Bradley Logan wrote:
I have been playing with the DataControl Control in an attempt to
understand how it works.
I have created a small openbase database with one Table. The table has
several columns.
The RB frontend is a window with statictext controls that name the
editfields. I have created a DataControl and an Enter, Delete,
NewRecord and Update Button. The buttons are all bound to the
DataControl and the appropriate pushbutton Object binds are selected.
The editfields are appropriately bound tothe DataControl. I have
entered four records.
The DataControl obediently finds first, next, previous and last
records.
It works as I would have thought EXCEPT when you push the Enter,
Delete or NewRecord buttons, you can no longer use the DataControl to
find first, next, previous or last records.
What gives?
TIA
Brad
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-nug-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-nug-digest at lists dot realsoftware dot com>
---
A searchable archive of this list is available at:
<http://support.realsoftware.com/listarchives/search.php>
Unsubscribe:
<mailto:realbasic-nug-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-nug-digest at lists dot realsoftware dot com>
.
|