William
Fri May 09 22:32:00 CDT 2008
IIRC (I'm on the road and don't have a copy with me) the first couple of
chapters address architecture but the Using TableAdapter chapter gets into
more detail on dos and don'ts.
--
__________________________________________________________________________
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)
____________________________________________________________________________________________
"Willian Lopes" <willian@transespecialista.com.br> wrote in message
news:80A24681-7A71-4CEE-A42F-EE31F4A59B07@microsoft.com...
> Is there a specific chapter that give me answers about that questions?
>
> "William Vaughn [MVP]" <billvaNoSPAM@betav.com> escreveu na mensagem
> news:589BE313-ABC8-4802-AB8C-3685E764C159@microsoft.com...
>> It's available everywhere technical books are sold see:
>>
http://www.bestwebbuys.com/0321243625
>>
>>
>> --
>> __________________________________________________________________________
>> 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)
>> ____________________________________________________________________________________________
>> "Willian Lopes" <willian@transespecialista.com.br> wrote in message
>> news:35415ECD-9264-452E-8CDF-940FCA1E1F7A@microsoft.com...
>>> Thanks for answer. About your book, is it already available for buing?
>>> What store?
>>>
>>>
>>> "William Vaughn [MVP]" <billvaNoSPAM@betav.com> escreveu na mensagem
>>> news:A5E3A5E3-0910-4F04-9C5C-B6E0480D0471@microsoft.com...
>>>> Willian,
>>>> Ah, I see any number of issues here. First, you should not plan to
>>>> bring all of your tables into memory using a Data Source / TableAdapter
>>>> code generator. This is not only expensive (it consumes a lot of
>>>> memory), it makes your application slow and yes, it can induce locks.
>>>> As I discuss in my book (at length) there are far better strategies but
>>>> unfortunately, the VS tools don't really lead you toward them.
>>>> Again, the book shows how to write a query and either use it to
>>>> populate a DataTable (in a dozen ways) or to feed a report. I have an
>>>> entire chapter on using the ReportViewer control that I think will be
>>>> of a lot of help.
>>>>
>>>> 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)
>>>> ____________________________________________________________________________________________
>>>> "Willian Lopes" <willian@transespecialista.com.br> wrote in message
>>>> news:7370EC2F-B705-4CF0-9E5D-6FA8380BB84E@microsoft.com...
>>>>> Hi!
>>>>> I´m a newbie with C# and .NET. I´m professional programmer with Delphi
>>>>> and I
>>>>> migrating from Delphi to C# with .NET
>>>>> .
>>>>> My questions are:
>>>>>
>>>>> 1) I´m using a single connection string into my application with a
>>>>> unique
>>>>> DataSource. May I load ALL my tables on this unique DataSource and use
>>>>> only
>>>>> data typed objetcs? Will this cause any conflict into database (a
>>>>> lock)?
>>>>>
>>>>> 2) How do I use a query? I want use a query to mount a report. How do
>>>>> I do
>>>>> this?
>>>>>
>>>>> 3) If I load all my tables on a unique DataSource will I use to much
>>>>> memory?
>>>>>
>>>>> Sorry my poor english, I´m not a native english speaker!
>>>>>
>>>>> Thanks for help!
>>>>>
>>>>> Willian Lopes
>>>>>
>>>>
>>>
>>
>