dsgetproperty resource limit? (None Specified)
At 23 FEB 1999 05:17:03PM Craig Buckley wrote:
We are using ODBC to access some foxpro tables. We have a line of code that states:
DSGETOK=DSGETPROPERTY(HDS,DS_RECORD$,PROJKEYS,'')
This has been working fine until recently. Our connection and dataset definitions have not changed. The only thing that has changed is the volume of records in the Foxpro table. We rewrote our dataset select script to bring back only a subset of the foxpro table instead of the whole thing and the DSGETPROPERTY again worked fine. Its pretty clear that our list of keys returned by accessing the DS_RECORD$ property has gotten too big.
QUESTION:
How big is too big. Is this a 64K thing?
At 24 FEB 1999 08:24AM Cameron Purdy wrote:
Craig,
It is a 64k thing. You can get a range of rows out at a time … like "1 to 100, 101 to 200, …".
Cameron Purdy
Revelation Software
At 24 FEB 1999 03:06PM [email protected] wrote:
Craig,
Yeah .. it is just as limited as OI
But that is why we use the xo function for any codings needed.
[email protected] onmouseover=window.status=imagine … ;return(true)"
David Tod Sigafoos ~ SigSolutions
voice: 503-639-8080
At 26 FEB 1999 09:53AM Cameron Purdy wrote:
dsig,
Yeah .. it is just as limited as OI
The DataSet is limited to roughly 520,000 rows, each of which can contain columns whose values are limited to 64k. The DataSet can be accessed from BASIC+ a cell, set of cells, row, set of rows, or entirely at a time. Similar to an Edit Table, which also can handle ]64k, if the data exceeds 64k, it reports null if you ask for all of the data.
But that is why we use the xo function for any codings needed.
The XO interface is a row-at-a-time. If you worked with the DataSet in the same manner, the end result would be the same. However, for a single pass through the data, the XO interface is a little more efficient since it does not cache the results locally.
Cameron Purdy
Revelation Software