Hi George,
I think we may be talking at crossed purposes here. What I'm trying to do is emulate the functionality in the "Records to fetch at a time" and the "Maximum records to fetch" spinners in the Tool/Options/Remote data tab. I want to be able to limit the number of records that a user can bring down off the back end from a SQL pass through query created at run time. We have some multi million row tables that a user could possibly bring across and that would be a Bad Thing. If I were using remote views, I could set them with dbsetprop(). I'm looking for a way to limit it for SQL pass through. Thanks.

Gary




>>George,
>>Thanks for the quick reply.
>>>I'd try to limit the amount of data returned...
>>How? I don't see a SQLSETPROP argument that, for example, will let me set a max rows returned to 1000. How does the view designer's advanced query option do it? I would assume that we can somehow get to the same OBDC properties, but maybe not.
>>
>Gary,
>
>It's not in ODBC, but rather in how you specify the retrieval criteria. For example, dividing 4,096 (the packet size) by the record size will tell you how many records can fit in one packet. That's a starting point for your designing the retrieval criteria. You want to limit the number of trips over the wire.
>
>There's no fixed number of records that will guarantee the efficient transmital of the data because of differing record sizes. That's why I mentioned trying to keep the record width as narrow as possible in the design stage, because it will allow more data to be sent than otherwise.