Re: C#, ADO.NET and MS-SQL

From: Daniel Billingsley (dbillingsley_at_NO_durcon_SPAAMM.com)
Date: 07/19/04 

Date: Mon, 19 Jul 2004 10:13:49 -0400

I apoligize for my answer. I was trying to rush out of here and just
shouldn't have answered.

But it's still true that you've asked some very BIG architecture-level
questions.

Perhaps if you asked specific questions one by one it would be better.

As for this example below - I'm not sure what you mean by "in a position".
There's lots of different ways to accomplish what you describe. Some
people/models avoid datasets altogether and use business object classes to
gather and valid the information. They may fire a stored procedure - so
there would never actually be a dataset at all.

As for the 35,000 record issue - that's a general design problem which has
also been solved numerous ways. One way is instead of having a combo box
(where listing 35,000 choices wouldn't be real helpful) there is a search
button next to the field that opens up a more sophisticated search form. As
someone else mentioned, you could also use some sort of filtering to narrow
the 35,000 records down to a small bunch the user is *likely* to select from
in the first place. Maybe a combination of the two.

But the point is there's nothing inherent in ADO.NET that really prohibits
or limits your ability to make it work however you want.

"DJ van Vliet" <dougie@global.co.za> wrote in message
news:cdbgvh$bel$1@ctb-nnrp2.saix.net...
> Thanks for the reply,
>
> I have a copy of MS ADO.NET step by step and Chris Sells' Windows forms
> programming in C#
>
> The problem is that all these books and articles show pieces of an
> application - e.g. a DataGrid or a Combo/ListBox containing lookup
> tables. What happens if there are 35,000 records that could be
> selected? I do not want to bring all the records across. This means
> interactive connection to the database while the user is busy capturing
> - not exactly a distributed method!
>
> Let me try and explain it better. (Maybe a short example.)
>
> The user requires a new purchase order.
>
> Known:
> Layout of Order header, a supplier is required and Items will be ordered.
>
> I need to build up a DataAdapter/DataSet as the new order is being
captured.
> Two tables - Header and Details.
>
> Header: selection of Ledger and Supplier.
> Details: selection of Store and Items
>
> Will the DataAdapter/DataSet be in a position to use the Update, Insert
> and Delete commands to commit changes back to the database?
>