loquin

Do you really need to return all million records? Or is there some distinguishing characteristic that you can use to limit the amount of records. i.e. is there a indexed field that is sequenced, for instance? Or a date field that could be used to break the dataset into smaller chunks. If this is something that needs to be done on a regular basis, it would be worth your while to add an indexed field, auto filled from a sequence for this very purpose. Then, you can build a stored procedure in Oracle to return only the data you request. And, being indexed, the query wouldn't take long at all, whether the records were from the first 100 records, or the last.

I've just started connecting to the Oracle database at work with .Net, and the only way I've been able to get connected is with ODBC or OLEDB. (We have an older installation of Oracle 6.3.7 - the upgrade to 8i is to take place in a couple of months, and the oracle .Net provider requires 8.i or greater on the client.) As with VB, you need to make sure that the project refereces ADODB if you follow this approach.. Project Add Reference then select adodb.

or even better, cd.CommandText = "SELECT * FROM Result WHERE User_ID='" & name & "'"