Michael D. Reed wrote:
Quote:
I have two tables in an Access database with a Many-to-Many
relationship,
there is a connection table. The tables are [Product Line],
[Factors], and
the connection table is [Product Line performance Factors] this is a
standard Many-to-Many relationship in that the connect table only has
two foreign key
columns one for each of the other table primary keys, a very
straightforward
setup.
>
The above is setup in a data set in a Data Set called
Oops, time for my standard "dotnet" reply:
There was no way for you to know it (except maybe by browsing through some
of the previous questions in this newsgroup before posting yours - always a
recommended
practice) , but this is a classic ADO newsgroup. ADO.Net bears very little
resemblance to classic ADO so,
while you may be lucky enough to find a dotnet-knowledgeable person here who
can answer your question, you can eliminate the luck factor by posting your
question to a group where those dotnet-knowledgeable people hang out. I
suggest microsoft.public.dotnet.framework.adonet.
Oh wait, this is a crosspost ... well, you've included two irrelevant
newsgroups in your crosspost list. I encountered this post in .data.ado,
which again, is a classic ADO group. The other irrelevant group is the
vb.database group, which again, has nothing to do with .Net. Best practice
is to limit your post to a single newsgroup (the csharp group was definitely
relevant, and you will probably get good help there) ... if you mistakenly
pick an irrelevant group, someone will steer you in the right direction
(politely, I hope).
Quote:
rows that it refers to. Do I have to revert to a separate quire to
perform
this operation?
That would be my preferred way of doing it, but perhaps the dotnet guys can
steer you to a builtin way.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"