By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,682 Members | 1,368 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,682 IT Pros & Developers. It's quick & easy.

Relations in Datasets

P: n/a
a
Hey,

I am building a Database App using VB.NET instead of MSAccess. I need some
tips for the data access strategy. I like the 'Microsoft Application Blocks
for .NET' approach, but am curious about relationships.

As an example, one section will be Document Tracking. A Document has one
Author (int field in the tblDoc table), one Type (int field in the tblDoc
table), possibly many WorkAreas (Many_to_Many with another table).

Am I better off manually grabbing DataSets, one for each int field, and then
manually binding 'dropdown' boxes on my form, or should I use Relationships
in the DataSet?

Also, I need some input about the ManyToMany deal. Is a PopUp form the best
way to go?

Please Advise.
Kevin
Nov 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Kevin,

When deal with Many-to-Many relationship, it is better to convert it to
"one to many to one". For example, we have a "Books" table and a "Author"
table. A book may have multiple authors and an author can have many books:

Books
---------------------
BookID, AuthorID

Authors
---------------------
AuthorID, BookID
You may add one table "BooksToAuthors", to present the relation between
Books and Authors. The three tables will be like:

Books
---------------------
BookID

Authors
---------------------
AuthorID

BooksToAuthors:
---------------------
BooksToAuthorsID
BookID
AuthorID

hope this help,

Luke
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)


Nov 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.