Page 2 of 2

Re: Cursorlocation = server

PostPosted: Wed Jun 15, 2016 3:52 am
by fieldhopper
thx for your suggestion. It will be nice if there is someone, who used the option =server, to help.

Re: Cursorlocation = server

PostPosted: Fri Jun 17, 2016 5:14 pm
by Neosoft Support
I assume that you're using CursorLocation=server because your database is very large. That can work under certain conditions, but many database functions are limited or don't work at all.

Instead you might experiment with using a 'LIMIT' type query so that DBPro doesn't try to read the whole database into memory. You can use the dbpExecSQL action to open a large table/worksheet instead of dbpOpenTable. This will allow you to limit the number of records returned. For example, the following will display just the first 50 records from the Contacts table:

dbpExecSQL "AddrBook" "SELECT TOP 50 * FROM Contacts" ""
dbpShowGrid "AddrBook" "Contacts" "Rectangle1"

You could use other types SQL queries to limit the number of records displayed at one time. The trick is to avoid trying to display millions of records at the same time.