Just a note to those who send sample apps of issues they face. Each one is
taken and integrated into a test application that I have. This way, with
each release I will be able to assure that an issue that is fixed will
remain fixed. So, sending simple sample apps is a great way to assure a
needful aspect of IBO remains vital. Especially the ones that are atypical.

Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Jason Wharton
> Sent: Thursday, February 22, 2007 1:10 PM
> To: IBObjects@yahoogroups.com
> Subject: RE: [IBO]Error returned due to slack syntax in 4.7.16
>
>
> Paul,
>
> > Following on from previous discussion about needing to
> > tighten up SQL syntax
> > for this release I was wondering if it would be possible to
> > improve the
> > error reporting on this.
> >
> > My latest problem is an access violation when preparing the
> > following SQL in a TIB_Query (code or designer)
> >
> > SELECT d.ICC_NO,d.invoice_number,d.customer_ac_no,
> > d.company,d.order_number
> > FROM ICC_HEADER D,CUSTOMER C,vatcodes v
> > WHERE d.vat_class=v.vat_code
> > AND D.company=c.co
> > AND D.CUSTOMER_AC_NO = C.ACCOUNT_NO
> > AND d.company='A'
> > AND d.invoice_number<=16000
> > AND d.invoice_number>=16000
> > AND bin_and(STATUS,3670016) in (0,2621440)
> > ORDER BY d.icc_no ASC
> >
> > The problem is fixed by putting the d. alias in front of
> > STATUS. Even a
> > catch-all like 'Incorrect Syntax' would do?
>
>
> Please send me a simple sample app with a DDL script to make
> the database.
> Test it once to make sure the error is still there.
>
> With this I should be able to quickly find out what is going
> on and fix it.
>
> Jason Wharton