Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Unions within 16bit Powerbuilder v5.03 usign Foxpro v2.5 with ODBC v.1.02

2 posts in PB Infomaker Report Writer Last posting was on 1997-11-07 20:21:20.0Z
113302.1413 Posted on 1997-11-07 20:17:19.0Z
Newsgroups: sybase.public.infomaker.general
Date: Fri, 07 Nov 1997 12:17:19 -0800
From: 113302.1413@compuserve.com
X-Mailer: Mozilla 2.01E-CIS (Win16; I)
MIME-Version: 1.0
Subject: Unions within 16bit Powerbuilder v5.03 usign Foxpro v2.5 with ODBC v.1.02
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 25
Message-ID: <348_3463774F.71D9@compuserve.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7403
Article PK: 244459

We are trying to use a UNION within the following setup

A 16bit application
Powerbuilder v5.03
Foxpro v2.5
ODBC v1.02

We can get UNIONS to work within Foxpro, but the problem arises when
using them within Powerbuilder

We get the following error

"SQL State = 37000 [Microsoft] [OBDC single tier driver] unsupported
SQL command in statement"

It seems to be to do with Foxpro interpretting a semi-colon as a
continuation charater and Powerbuilder interpretting a semicolon as a
terminator character.

We have tried to reconfigure the database terminator character to ` but
this gives a Syntax error instead.

SELECT A, B ;
FROM TABLE1 ;
UNION ;
SELECT C,D ;
FROM TABLE2 `

We have also tried setting delimitidentifier="Yes" without success
We know that this can be overcome by upgrading to ODBC version 2.0, but
we do not want to do this as it causes many other problems.

Any suggestions would be much welcomed

Cheers!

Alasdair Thompson


Alasdair Thompson Posted on 1997-11-07 20:21:20.0Z
Newsgroups: sybase.public.infomaker.general
Date: Fri, 07 Nov 1997 12:21:20 -0800
From: Alasdair Thompson <AThomp3467@aol.com>
X-Mailer: Mozilla 2.01E-CIS (Win16; I)
MIME-Version: 1.0
Subject: Re: Unions within 16bit Powerbuilder v5.03 usign Foxpro v2.5 with ODBC v.1.02
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 32
Message-ID: <348_34637840.6351@aol.com>
References: <348_3463774F.71D9@compuserve.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7402
Article PK: 244457


113302.1413@compuserve.com wrote:
> SORRY - PLEASE REPLY TO

AThomp3467@aol.com
AS I HAVE CANCEL MY COMPUSERVE ACCOUNT!!

> We are trying to use a UNION within the following setup
>
> A 16bit application
> Powerbuilder v5.03
> Foxpro v2.5
> ODBC v1.02
>
> We can get UNIONS to work within Foxpro, but the problem arises when
> using them within Powerbuilder
>
> We get the following error
>
> "SQL State = 37000 [Microsoft] [OBDC single tier driver] unsupported
> SQL command in statement"
>
> It seems to be to do with Foxpro interpretting a semi-colon as a
> continuation charater and Powerbuilder interpretting a semicolon as a
> terminator character.
>
> We have tried to reconfigure the database terminator character to ` but
> this gives a Syntax error instead.
>
> SELECT A, B ;
> FROM TABLE1 ;
> UNION ;
> SELECT C,D ;
> FROM TABLE2 `
>
> We have also tried setting delimitidentifier="Yes" without success
> We know that this can be overcome by upgrading to ODBC version 2.0, but
> we do not want to do this as it causes many other problems.
>
> Any suggestions would be much welcomed
>
> Cheers!
>
> Alasdair Thompson