🚀 go-pugleaf

This is what I found out from MSDN, MS TechNet, and the VB guys here:

The select statement was still processing (13000 records) the records.  The
go bottom/go top forced the process to finish.  Therefore, allowing the edit
to be saved.

Now, how do I limit the number of records returned to, say, 50 or 200
records?  Is there a rowcount() type option in 5.6?


Christopher F. Neumann wrote in message <6p2oo2$kpr2@forums.borland.com>...
>OK, this is becoming ridiculous!  If I execute a GO BOTTOM and then a GO
TOP for the alias, NO PROBLEM WITH EDITS STICKING!!!  If I only skip 100
records, the edit will NOT stick.  Can someone explain this?
>
>Christopher F. Neumann wrote in message
<6p2ldo$k7225@forums.borland.com>...
>>OK, getting closer.  When my browse only has a few records listed, the
edit sticks.  When the browse has several records, it returns "connection is
busy with results for another hstmt".  There is no other user, after this
error, if I go right back and limit search to a few, the edit will stick!
>>
>>Obvious question, does that error have to do with the number of records
returned from the select statement that is linked to the browsebox?
>>
>>It is that a field in the SQL view is being altered and the value not
being saved.
>>
>>It is a table that is selected from a browse (5.6) and brought into a
form.  The entryfields that are datalinked to the fields are changed, but,
the changes dont go back to the record.