There are several "good" ways but the "best" way really depends on a lot of factors including:
a.. Your skill and experience
b.. The existing DBMS infrastructure
c.. The number of people sharing the database
d.. How large is the database
e.. How large are the structures to be fetched into client memory
f.. Whether or not your DBA permits base-table access
There are far more, but you get the idea. I expect my book (see title below) would be ideal for you needs. It discusses all of these issues and more and focuses on Windows Forms application development.
hth
--
__________________________________________________________________________
William R. Vaughn
President and Founder Beta V Corporation
Author, Mentor, Dad, Grandpa
Microsoft MVP
(425) 556-9205 (Pacific time)
Hitchhiker’s Guide to Visual Studio and SQL Server (7th Edition)
http://betav.com http://betav.com/blog/billva
____________________________________________________________________________________________
"Kursat" <(E-Mail Removed)> wrote in message news:#(E-Mail Removed)...
> Hi,
>
> I am writing a Windows Forms application. The application should fullfill
> these functionalities :
>
> - Presenting data on GUI controls (Grids, TextBoxes, ComboBoxes, etc...)
>
> - Filtering data depending on given criterias
>
> - Manipulating data (insert, delete, update)
>
> - Presenting related data on different GUI controls in master-detail manner
>
> - Reporting data (on built in CrystalReportViewer)
>
> I am using VS 2008 and SQLServer. It seems there is too many options for
> working with data (Data adapters, DataViews, TypedDataSets...). What is the
> best and most up to date method for working with data to implement above
> functionalities?
>
> Thanks in advance
>
>
Similar Threads
