Disconnected Data - good or bad? (performance)

Can anyone please explain me the real advantage of using disconnected dataset in an OLTP system?

For example, suppose I want to connect to an Oracle table containing 1M rows. If I make a front end using Access or Developer 2000, I can scroll thru the records from front end at lightning speed. However, if I create a VB.NET form to show the records, thru disconnected dataset, it takes several minutes to load the whole things. I tried with far less rows (appx 20000) but still it takes long time to show the records.

My question is, how can it be done in VB.NET disconnected recordset concept?

I think, one often claim advantage of disconnected recordset is that it does not take up "valuable" resource by several connections. But is it true for all databases? Oracle has shared server feature which allows several thousand concurrent users without any problem.

Can anyone please explain the things?

Thanx a lot

Honestly, I'm not the right one to discuss about ADO.NET and DATASET. Until now, I have always used ADO, because I want to be able to lock pessimistichly the pointed record. Anyway I think the real advantage is when you have to reach your DB via internet, or another kind of connection with a limited baudrate. Anyway I'm curios to know the opinion of other more experienced friends. I'm a beginner and probably I'm loosing some important aspects.....and excuse my english! :)

Well, 1M records might be a little slow...

20,000 shouldn't take any considerable time.

What OLE provider are you using?

Are you using BeginLoadData to suppress notifications until you have read the Dataset?

A strongly-typed dataset can offer performance gains...

A generic dataset that uses ordinals will offer immense gains over a dataset that looks up everything by column or table names.

I tried to connect with Oracle & SQL Server (SqlDb & OleDb).

I mainly used data form wizard.

Can you give me some code example showing how the incident can be made faster?

:)

Thanks