>>What you are doing should work unless the ConnectHandle is wrong. Does cursorgetprop('connecthandle') return the same value as your toaccess variable? You can also use DBGetProp('connection_name','connection','asynchronous') tp see what it is in the DBC.
>>
>>I would also make sure FetchSize and MaxRecords to -1 [use DBGet/SetProp].
>
>Thanks for the help, Mark. I like the "what you are doing should work" part :) At least I'm learning something :) :). I'm going to go check to see if cursorgetprop('connecthandle') returns anything. Like I said, when I put toaccess in the debugger I got Can not evaluate expression. I'll also check out the dbGetProp bit.
>
>And if I'm understanding you, I should change FetchSize and MaxRecords to -1 and should use the DBSetProp function to do so. I'm presuming FetchSize and MaxRecords being set to -1 will mean that there's no constraint... it will get as much as it can handle? And I should do it within the function instead of the designer becuase there's something obviously wrong with the connection in designer? Does that sound about right?
>
>Thanks again for the help.

The connection designer and view designer should be able to set these proerties for you. I suggested using the native functions so you could see what the existing conditions are. This should help in finding out what is wrong by looking at current settings, changing 1 then retrying. If you do not know what you started with and just change 1 or more parameters, then you won't know what fixed the problem.

The -1 says to fetch all records at once. I suggested this because this is what got me a connection busy message when opening a view that I knew had exactly 1 record. I told the VD to select exactly 1 record. I know the table had 1 record because it was the DUAL table in Oracle which contains exactly 1 record. The purpose of the table is for issuing a SQL that has no applicable source table to select from but by definition every SQL has to have a FROM SOMETABLE clause. As soon as I changed FetchSize back to -1, the busy error disappeared. Go figure.