There are no issues with VB and tables in the DataSet designer. But what I
usually do is separate out the tables into separate DataSets based on area or
functionalty. For example all Sales Order data in one, Customers in another
etc. Makes it more understandable in the long run.
David
======================================
David McCarter [Microsoft MVP]
www.dotNetTips.com
David McCarter''''s .NET Coding Standards available at:
http://www.cafepress.com/geekmusicart.1654787045
"johnb" wrote:
> Hi
> As a newbe to the vb.net environment I'm unsure that I'm going the right
> way. I've created a Connection to SQL express where I've got 20 tables.
>
> When I open the DataSet designer in vb its a jungle of all the tables. I
> can't find a zoom factilty as you have in Project. so I'm thinking have I
> done this the right way.
>
> How does VB handle large number of tables in the dataset designer?
>
> TIA
> johnb