error 3296

[mark r]

I am building SQL code to run a report using
dbengine (0)(0).querydef

I am
getting error message 3296
JOIN EXPRESSION NOT SUPPORTED
HELP: ON statement of join contains too many tables

the line that builds the join is:
cnst strcstub2 = "from table1 inner join table2 on
table1.id = table2.id"

this is the same line of code that works in a query I
already have.

I am using ACCESS2000

 

[Marshall Barton]

I am building SQL code to run a report using
dbengine (0)(0).querydef

I am
getting error message 3296
JOIN EXPRESSION NOT SUPPORTED
HELP: ON statement of join contains too many tables

the line that builds the join is:
cnst strcstub2 = "from table1 inner join table2 on
table1.id = table2.id"

this is the same line of code that works in a query I
already have.

If Allen's suggestions haven't penetrated this issue, I'm
not sure anyone can do any better.

I think that we need to see the rest of the code after
you've edited it to eliminate any potential confusion caused
by newsreader line wrapping.

What I suspect you have somewhere (in yet to be posted code)
is a concatenation of the various pieces of the complete SQL
statement and one or more of the pieces is missing a
leading/training space.

 

[mark r]

Your record is still perfect with me.

What I suspect you have somewhere (in yet to be posted

code)is a concatenation of the various pieces of the
complete SQL statement and one or more of the pieces is
missing a leading/training space.

You were right!! I crawled back through the code and that
was the problem..it works perfect.

I really appreciate that YOU went the extra mile to make
the extra comment:

pieces is missing a leading/training space.

Clipping and posting code is not always necessary, since
my platform is not hooked up to the internet it requires
cut and paste and diskette and privacy issues and is
somewhat inconvenient, it assumes I am too daft to take a
suggestion and work with it (I admit I am new and not a
programmer by training but I am not daft)

not sure anyone can do any better

The word penetrate smacks of insult

As it turns out, Allen's suggestion was perfect and
insightful but gave up trying to empathize with a non
programmer as to likely pitfalls. One does not have to
see code to point out a list of likely pitfalls.
Surprisingly to you, I was actually capable of finding the
bug myself. It even surprised me.







Your

 

[Marshall Barton]

[snip] One does not have to
see code to point out a list of likely pitfalls.
Surprisingly to you,

Come on Mark, you don't really want a bunch of people just
guessing what might be wrong with some code only you can
see. Your development setup may be difficult to deal with,
but the responders you hope to receive help from don't
really have the time to spend speculating on skimpy clues.