Classes and collections vs. virtual tables (datasets)

25 Apr 2006 10:07 PM

M Harris

We are developing an application (using .Net in MS Studio 2003 using the
Access jet engine as a backend) that is doing quite a bit of number
crunching. The first part of the application was written using collections,
but we have now found that manipulating the data in virtual tables
(datasets) seems a better way to go. However, we have not attempted to
rewrite the previous code to compare the processing of one compared to the
other. Has anyone else had experience with this?

25 Apr 2006 11:29 PM

tommaso.gastaldi

Hi M Harris,

I had the the opposite experience. I started storing data into datasets
and datatables. But after some experiments returned to the simple and
effective arraylist, unbeatable as to performances... :)

Anyway, in general, probably the best decision depends on the general
architecture of you program and for the tasks you have to do. My
current thinking is that one should use the dataset only if he has to
maintain a sort of local database (tables, relationships,...) ...
Personally, I tend to stay far from datatables when possible ...

just my 2 cents

-tom

26 Apr 2006 5:15 AM

Michel Posseth [MCP]

This is the same as

what is better a speedboat or a cruise liner ?

well if you want to go fast from a to b on a short distance i would prefer
the speedboat , however for crossing the ocean i would go for the cruise
liner

my personal aproach is :

go for the most lightweight aproach when apropriate and possible and now
when to hump on the cruiseliner ( you see often people extend there
speedboat untill it is almost sinking on its weight , it would have been
better to use the cruiseliner instead )

regards

Michel Posseth [MCP]

Show quoteHide quote

"M Harris" <mhar***@revenue.state.il.us> schreef in bericht
news:%23QuqmSLaGHA.3896@TK2MSFTNGP05.phx.gbl...
> We are developing an application (using .Net in MS Studio 2003 using the
> Access jet engine as a backend) that is doing quite a bit of number
> crunching. The first part of the application was written using
> collections,
> but we have now found that manipulating the data in virtual tables
> (datasets) seems a better way to go. However, we have not attempted to
> rewrite the previous code to compare the processing of one compared to the
> other. Has anyone else had experience with this?
>
>

26 Apr 2006 8:17 AM

Cor Ligthert [MVP]

Lol but true, do you maybe have a free sight on the harbour?

Cor

26 Apr 2006 6:00 PM

Michel Posseth [MCP]

>>Lol but true, do you maybe have a free sight on the harbour?

No.... but i live nearby the harbour ( a view to the harbour has a big
price these days in Rotterdam :-)

regards

Michel

Show quoteHide quote

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> schreef in bericht
news:e9eZYmQaGHA.1348@TK2MSFTNGP05.phx.gbl...
> Lol but true, do you maybe have a free sight on the harbour?
>
> Cor
>

26 Apr 2006 5:32 AM

Cor Ligthert [MVP]

M Harris,

Datasets and Datatables are a kind of ultime implementations of Classes
which holds collections.

With that taking all the overhead from those classes which simple arrays
don't have.

Therefore if you want only an simple array, than you can use a simple
collection. If you want an class which has everything that you need to
handle data in it, than you can take a dataset (although it is in my opinion
not yet ready, there can be even more in it).

I hope this helps,

Cor

Show quoteHide quote

"M Harris" <mhar***@revenue.state.il.us> schreef in bericht
news:%23QuqmSLaGHA.3896@TK2MSFTNGP05.phx.gbl...
> We are developing an application (using .Net in MS Studio 2003 using the
> Access jet engine as a backend) that is doing quite a bit of number
> crunching. The first part of the application was written using
> collections,
> but we have now found that manipulating the data in virtual tables
> (datasets) seems a better way to go. However, we have not attempted to
> rewrite the previous code to compare the processing of one compared to the
> other. Has anyone else had experience with this?
>
>