NESTED JOINS

[Guest]

I'm a SQL 2000 developer and I'm used to simple, straight forward queries
whenever I have to relate more than five tables throught INNER JOINS.

Now, I have to make an application easy enough so that the user by just
selecting certain criteria from options control boxes that application shows
the results on a grid.

The database I'm trying to use is Microsoft Access 97(JET 3.51), but when it
comes to build the quieries for several tables I come across the problem with
the NESTED INNER JOINS that Access requires in the queries.

My problem is not the WHERE, nor any grouping function but with the INNER
JOINS.
Is there a simple method to guess what MS Access requires to have the SELECT
clause with no errors?

I try to copy an paste queries from SQL2000 on Access, but they don't work
well.

So, I'm looking for a methodology that solves this. I don't want to bring
the queries here to be solved. I just need a link, a method for relating the
NESTED JOINS that MS Access requires...

So far, MS ACCESS QUERY BUILDER works well, but I need that my application
WRITES the queries... do you understand my problem?


Thank you.

 

[Amy Blankenship]

Not really. What's the actual task you are hoping to accomplish, and what
error are you getting, with what SQL?

 

[Guest]

I'm trying to build an internal Query builder for a VB6 Application, it must
use a private MS ACCESS database, and I need some documentation for the
NESTED JOINS, since I've found them difficult to buil, in the way MS ACCESS
97 does it.

 

[Amy Blankenship]

I asked for several details from you, and you really didn't provide any of
them. The internal query builder is doing what? What business need is it
satisfying? Possibly there is some other approach that would solve the
business need. Regardless, since you refuse to provide the error and the
SQL you've attempted, you are not an easy person to help.

Maybe someone else will have some better luck reading your mind.

 

[Guest]

Thank you gor your kind appreciation.

--
Rick

I asked for several details from you, and you really didn't provide any of
them. The internal query builder is doing what? What business need is it
satisfying? Possibly there is some other approach that would solve the
business need. Regardless, since you refuse to provide the error and the
SQL you've attempted, you are not an easy person to help.

Maybe someone else will have some better luck reading your mind.