1. Strongly typed DataTable with loosely typed DataSet
I have not played with strongly typed dataset much.
If the answer is obvious, please pardon me.
Strongly typed dataset is exciting.
I wonder if I can create few strongly typed data tables
and assemble a data set at runtime.
Dataset1: Order, OrderItems
Dataset2: Invoice, Orders
Dataset3: Customer, Invoices
Dataset4: Customer, Users, UserProfile
As you can see, Customer, Invoice, Order, and OrderItem
are combined in different ways in different application context.
In my 'real-world' there are many more base types
with numerous combinations in different application scenarios.
(Most of the scenarios are read-only, few updateable)
Q1: If I generate two strongly typed datasets, say for example
Dataset1 and Dataset2, will I end up with two distinct
Order types (Identical, but distinct for the type system)
Q2: I would like to define few strongly typed DataTables,
but assemble loosely typed dataset at runtime,
and load data using DataAdapters which will
fill the Customer DataTable irrespective of
which dataset it is used?
2. CZ, the place to buy portables
3. Strongly Typed Datasets, New Rows, and Concurrency
4. PS -> SYS fonts
5. Strongly Typed DataSet stops returning rows
6. Part time Consulting
7. Convert Strongly Typed Object to Un-typed
8. netcom replies
9. Are strongly typed DataSet's more preformant?
10. Experiences with DataReader \ DataSet \ Custom Strongly Type DataSet
11. Major Problem downcasting from DataSets to Strongly typed datasets across dlls
12. Problem Casting from Dataset to Strongly Typed Dataset
13. Strongly typed CUSTOM Dataset DBNull handling vs generated dataset