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 16 bit Powerbuilder v5.03 with Foxpro v2.5 and ODBC v1.02

2 posts in PB Infomaker Report Writer Last posting was on 1997-11-07 20:23:27.0Z
Alasdair Thompson Posted on 1997-11-07 20:23:27.0Z
Newsgroups: sybase.public.infomaker.general
Date: Fri, 07 Nov 1997 12:23:27 -0800
From: Alasdair Thompson <AThomp3467@aol.com>
X-Mailer: Mozilla 2.01E-CIS (Win16; I)
MIME-Version: 1.0
Subject: UNIONS within 16 bit Powerbuilder v5.03 with Foxpro v2.5 and ODBC v1.02
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 27
Message-ID: <348_346378BF.668F@aol.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7401
Article PK: 244458

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


Terry Dykstra Posted on 1997-11-07 19:10:41.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: UNIONS within 16 bit Powerbuilder v5.03 with Foxpro v2.5 and ODBC v1.02
X-Newsreader: Microsoft Internet News 4.70.1161
Date: Fri, 07 Nov 1997 14:10:41 -0500
Lines: 38
Message-ID: <348_01bcebb9$4c481200$8366e4cf@tdykstra.cfol.ab.ca>
References: <348_346378BF.668F@aol.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.powersoft.com
Xref: forums-1-dub sybase.public.infomaker.general:7400
Article PK: 244455

Why are you putting semi-colons at the end of each line? They are not
required
SELECT A, B
FROM TABLE1
UNION
SELECT C,D
FROM TABLE2

The terminator character is only required in the db-painter.

Terry Dykstra (TeamPS)

Alasdair Thompson <AThomp3467@aol.com> wrote in article
<346378BF.668F@aol.com>...
> 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
>