Hi

Sitting here looking like a stunned mullet!

Getting this error on a bit of SQL - DBISAM v3.30
------------------------------------------------------------------------
DBISAM_SQLPARSE (11949)   SQL error - "Internal join error - JOIN clause
expression for table "O" is invalid.

This error occurs when any error occurs during the parsing,
preparation, or execution of an SQL statement.  The message will give
the specific details of the error and why the error occurred.
------------------------------------------------------------------------

The offending SQL is below.  Can't see what is wrong, can anyone please
....
------------------------------------------------------------------------
UPDATE MEMORY T1

SET T1."PaymentMethod" =
IF((B.fldOwnerPaymentType = 'Cheque') OR ((B.fldOwnerPaymentType =
'Hold') AND (B.fldPayeeBankDetailsAccountNo = '')) THEN  'CHQ'
ELSE IF (B.fldOwnerPaymentType = 'Hold' THEN 'DC'
ELSE 'CHQ')),
T1."Payee" = B.fldPayeeBankDetailsAccountName ,
T1."AccountNo" = B.fldPayeeBankDetailsBankBra_3 +
B.fldPayeeBankDetailsAccountNo,
T1."PayeeReference" = B.fldPayeeBankDetailsOtherPa_9 ,
T1."PayeeAnalysis" = B.fldPayeeBankDetailsOtherPa_8,
T1."PayeeParticulars" = B.fldPayeeBankDetailsOtherPa_7  


FROM MEMORY T1
LEFT OUTER JOIN "0tblOwner" O ON (O.fldOwnerCode = T1.InternalComments)
LEFT OUTER JOIN "0tblPayeeBankDetails" B ON (B.fldPersonCode =
O.fldPersonCode)
;
------------------------------------------------------------------------

I've tried substituting the ON with "(O.fldOwnerCode = 'xxxx') in case
it was a type mismatch.  O.fldOwnerCode is a string field.  Didn't make
and difference.  T1.InternalComments is actually a MEMO field that I'm
using during a data conversion.

Cheers

Jeff

--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz
+
Joan and Jeff Cook
The Cooks Oasis
www.cookislandsoasis.com

Jeff,

<< Getting this error on a bit of SQL - DBISAM v3.30 >>

I'm not sure what the issue is, but if you'd like to send me the empty
tables, I can at least trace it and tell you why it's doing what it is
doing.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> From: "Tim Young [Elevate Software]" <timyoung@elevatesoft.com>
> Subject: Re: Internal Join error has me beat!
> Date: Tue, 29 Jan 2008 15:46:58 -0500
> Message-ID:
> <939DB52E-0DA5-46F3-814D-E237DF1B6E24@news.elevatesoft.com> Lines: 14
>
> Jeff,
>
> << Getting this error on a bit of SQL - DBISAM v3.30 >>
>
> I'm not sure what the issue is, but if you'd like to send me the
> empty tables, I can at least trace it and tell you why it's doing
> what it is doing.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com


Thanks Tim

Tables and SQL on their way by email.

Cheers

Jeff

--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz
+
Joan and Jeff Cook
The Cooks Oasis
www.cookislandsoasis.com

Jeff,

Two things:

1) Your query uses LandordCode instead of LandlordCode.
2) The in-memory table does not contain an OwnerCode column.

There are some further errors after that, but they are self-explanatory.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote:

> Jeff,
>
> Two things:
>
> 1) Your query uses LandordCode instead of LandlordCode.
> 2) The in-memory table does not contain an OwnerCode column.
>
> There are some further errors after that, but they are
> self-explanatory.

Many, Many thanks Tim

1) was the real killer - I think that I might recompile DBSYS with a
Courier New font as my old eyes were obviously not seeing the missing
"l" in a proportional font.

But I should have seen (2)!

Meitaki Ma'ata

Jeff

--
Jeff Cook
Aspect Systems Ltd
www.aspect.co.nz
+
Joan and Jeff Cook
The Cooks Oasis
www.cookislandsoasis.com