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.

SQL Preview Syntax

2 posts in DataWindow .NET Last posting was on 2004-10-16 04:54:30.0Z
Paul SW Posted on 2004-10-15 21:43:17.0Z
Sender: 33f0.41704377.1804289383@sybase.com
From: Paul SW
Newsgroups: sybase.public.datawindow.net
Subject: SQL Preview Syntax
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <41704471.3404.1681692777@sybase.com>
X-Original-NNTP-Posting-Host: 10.22.241.42
X-Original-Trace: 15 Oct 2004 14:43:13 -0700, 10.22.241.42
Lines: 11
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 15 Oct 2004 14:43:16 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 15 Oct 2004 14:43:17 -0700
X-Trace: forums-1-dub 1097876597 10.22.108.75 (15 Oct 2004 14:43:17 -0700)
X-Original-Trace: 15 Oct 2004 14:43:17 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:548
Article PK: 124979

I'm seeing numeric placeholders, preceded by colons, in the
update statement for the sqlsyntax argument in sqlpreview.
In other environments, I've seen the actual values. Does
anyone know what causes this difference:

Update theTable set prim_id = :1, customer_name = :2, etc.

vs.

Update theTable set parim_id = 203, customer_name = "Sybase,
Inc.", etc.


Bruce Armstrong [TeamSybase] Posted on 2004-10-16 04:54:30.0Z
From: "Bruce Armstrong [TeamSybase]" <NOCANSPAM_bruce.armstrong@teamsybase.com>
Newsgroups: sybase.public.datawindow.net
Subject: Re: SQL Preview Syntax
Organization: TeamSybase
Reply-To: NOCANSPAM_bruce.armstrong@teamsybase.com
Message-ID: <1ba1n0t949mh9kh2q87jefkbiju56aei8b@4ax.com>
References: <41704471.3404.1681692777@sybase.com>
X-Newsreader: Forte Agent 2.0/32.652
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: 68-190-226-38.la-cbi.charterpipeline.net
X-Original-Trace: 15 Oct 2004 21:54:26 -0700, 68-190-226-38.la-cbi.charterpipeline.net
Lines: 49
X-Original-NNTP-Posting-Host: forums-2-dub.sybase.com
X-Original-Trace: 15 Oct 2004 21:54:27 -0700, forums-2-dub.sybase.com
NNTP-Posting-Host: forums-master.sybase.com
X-Original-NNTP-Posting-Host: forums-master.sybase.com
Date: 15 Oct 2004 21:54:30 -0700
X-Trace: forums-1-dub 1097902470 10.22.108.75 (15 Oct 2004 21:54:30 -0700)
X-Original-Trace: 15 Oct 2004 21:54:30 -0700, forums-master.sybase.com
X-Authenticated-User: ngsysop
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.datawindow.net:549
Article PK: 124975

Is this a DataWindow.Net question?

Turn off binding for the connection.

On 15 Oct 2004 14:43:17 -0700, Paul SW wrote:

>I'm seeing numeric placeholders, preceded by colons, in the
>update statement for the sqlsyntax argument in sqlpreview.
>In other environments, I've seen the actual values. Does
>anyone know what causes this difference:
>
>Update theTable set prim_id = :1, customer_name = :2, etc.
>
>vs.
>
>Update theTable set parim_id = 203, customer_name = "Sybase,
>Inc.", etc.

Bruce Armstrong [TeamSybase]
http://www.teamsybase.com

TeamSybase blogs:
http://www.teamsybase.net/blogs

Two 3rd party books on developing with PowerBuilder
http://www.pb9books.com?source=newsgroups

Need code sample? Check out CodeXchange:
http://www.codexchange.sybase.com

Preach the gospel at all times. If necessary, use words. - Francis of Assisi
http://www.needhim.org

---------------------------------------------------------------------
DISCLAIMER:

This newsgroup message is only intended for the recipient. Given that it
is a posting to a public newsgroup, that means if you can read this
message then you are the recipient. This message may contain information
that is confidential and protected from disclosure. And then again,
it may not.

Given that TeamSybase members are not employees of Sybase, the contents
of this message do not necessarily represent the views or policies of
Sybase. Given that TeamSybase is a diverse group of users of Sybase
products, the contents of this message do not necessarily represent the
views of a significant number of the members of TeamSybase. Given that the
author has multiple personalities and hears voices in his head, the contents
of this message do not necessarily represent his own views.