"Same Parent cannot be parent for 2 child tables"

[Vince Teachout]

"The Same Parent cannot be parent for 2 child tables" - Why the ****
NOT?!!!

I have a table with User ID, Division code field.

When I try and run the query wizard to select the User name and
division name from 2 other tables, using the fields as look ups into
those tables, I get the above error message.

Obviously, it's no problem doing this with SET RELATION, why should it
be a problem in SQL?

Is this a SQL limitation? A Wizard bug? Is there actually a good
reason why this isn't allowed? I'm coding around it for now, but this
is annoying. Any suggestions? (Other than telling me to lay off the
coffee....)

Ignore munged e-mail address above.
If necessary to reply via e-mail, please reply to:
caracal A T caracal D O T net

[Stephen Russell]

I don't have this problem with my queries or views. I'd stop using the M$
tool and code them by hand.

__Stephen

"Vince Teachout" <SendJunkMailTo@hotmail.com> wrote in message
news:d07g0to4sqdmrm066g60pdbk8ikvddrugj@4ax.com...
> "The Same Parent cannot be parent for 2 child tables" - Why the ****
> NOT?!!!
>
> I have a table with User ID, Division code field.
>
> When I try and run the query wizard to select the User name and
> division name from 2 other tables, using the fields as look ups into
> those tables, I get the above error message.
>
> Obviously, it's no problem doing this with SET RELATION, why should it
> be a problem in SQL?
>
> Is this a SQL limitation? A Wizard bug? Is there actually a good
> reason why this isn't allowed? I'm coding around it for now, but this
> is annoying. Any suggestions? (Other than telling me to lay off the
> coffee....)
>
> Ignore munged e-mail address above.
> If necessary to reply via e-mail, please reply to:
> caracal A T caracal D O T net

[Cindy Winegarden]

Wizards are by nature for "simple" needs only.

--


Cindy Winegarden

Microsoft Certified Professional, Visual FoxPro
Microsoft Visual FoxPro MVP

cindy.winegarden@mvps.org



"Vince Teachout" <SendJunkMailTo@hotmail.com> wrote in message
news:d07g0to4sqdmrm066g60pdbk8ikvddrugj@4ax.com...
| "The Same Parent cannot be parent for 2 child tables" - Why the ****
| NOT?!!!
|
| I have a table with User ID, Division code field.
|
| When I try and run the query wizard to select the User name and
| division name from 2 other tables, using the fields as look ups into
| those tables, I get the above error message.
|
| Obviously, it's no problem doing this with SET RELATION, why should it
| be a problem in SQL?
|
| Is this a SQL limitation? A Wizard bug? Is there actually a good
| reason why this isn't allowed? I'm coding around it for now, but this
| is annoying. Any suggestions? (Other than telling me to lay off the
| coffee....)
|
| Ignore munged e-mail address above.
| If necessary to reply via e-mail, please reply to:
| caracal A T caracal D O T net

[Vince Teachout]

Ok, so it's a Wizard limitation. Good. (I was able to do it by hand
without a problem). It's just frustrating to pick out the 40 or so
fields out of several files, and THEN be told it can't be done....



Ignore munged e-mail address above.
If necessary to reply via e-mail, please reply to:
caracal A T caracal D O T net