Out of Memory, Performance Issue

[indigo]

I have an Oracle table containing about 70000 records. The table is being displayed in a grid. Whenever a user selects all the records and then navigates to the end of the table the following behavior is observered.

On test machines with 512MB memory everything works fine. On the client machines which have about 64MB of memory, the user is given a message "Out of Memory" and the grid goes blank, apparently because the table is being deactivated. The user also notices that the mouse is very sluggish responding during this time.

Any idea what is causing this and how to fix it?

Thanks

 

[Marco Kalter]

You should not attempt to display a result set of 70,000 records in a TOracleDataSet. If the user navigates to the last record, all other records will be fetched as well.

If the "last" record is of particular interest to the user, you can either provide the necessary "order by" functionality, or you can provide QBE functionality to allow the user to limit the result set to those records that he or she is actually interested in.

------------------
Marco Kalter
Allround Automations

 

[indigo]

I have given the user the ability to make whatever query he wants. I don't really care that he selected all 70000 records. When this happens, it takes about six seconds and everything works fine except for those users that have a limited amount of memory on their PC. I just want to be able to prevent the "Out of Memory" error.

Is there a way to limit the number of records returned by the query even though the user returned them all?