>Hi John,
>
>Thanks for your help. However, it wouldn't be limited to only two cursors since all tables are depending on one another to get the data we actually need.
>
>The solution has been provided that we are going to move all data into one DBC, which is the best and easiest way out.
>
>The SQL statement immediately worked after that, so I'm all set with an ADO recordset and ASP will take it from there...
>
>Only thing I'm looking for now is how I can split the ADO set up into say 15 records at a time. I think there's a property for that...
>
>Johan IJzerman
>
>Digital Dynamics ITC

The property is Cachesize on the Recordset object.