>>>First item here? http://fox.wikis.com/wc.dll?Wiki~RemoteViewFAQ~Wiki
>>
>>Interesting. I wish there was simply a way to change
>> the fetchsize to avoid the problem to begin with...but
>> I don't see a way to do that..perhaps there is?
>
>Ask Cetin. I bet he knows. Also, MSDN had a couple hits through cursorsetprop().

yeah I did some googling and found a couple things. I'm going to go make sure I've got fetchsize set the way I want in all my remote views and add the other code I came up with for the sql passthough one. If nothing else I figure those waitwindows will at least let me see for sure if its the sqlpassthough causing the problem. I really didn't want to do it this way to begin with - but the choice was to either install the DB2 ODBC driver (which is a pain) on 3,000 workstations or to put it on one Oracle server. Sadly due to the security settings on the Oracle database I have to issue that "alter session global_names' thing for the connection string to be able to hit the db2 data via the db2 dblink in oracle - so I had no choice but to use the sql passthough. Hopefully these ideas here will get it working - it's actually going to be a pretty slick way of doing it once it's all working 100%.
Another strange thing here is that all of this only works if I'm using the Microsoft for Oracle ODBC driver - it doesn't work if you use the Oracle for Oracle ODBC driver. Thankfully the workstations are all using the MS one already.