Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to specify a new sql.ini path instead of the default

461 views
Skip to first unread message

Chetan

unread,
Jul 7, 2004, 9:50:33 AM7/7/04
to
Hi,

How would I specify a customised path instead of the default
path (sybase\ini\sql.ini) every time PB Application(Windows)
client connects to the sybase database server(Unix) in a
client-server environment using syc interface(o/c 12.5).

Thanks

Jim O'Neil [Sybase]

unread,
Jul 7, 2004, 12:07:40 PM7/7/04
to
That's governed by the value of the SYBASE environment variable, so
you could call the GetEnvironment/SetEnvironment Window APIs to tailor
this after your PB app starts, or you could start your PB app from a
BAT file in which you set the environment variable appropriately
before launching the EXE.

Jim O'Neil
Principal Technical Support Engineer
Sybase, Inc.
Concord, MA

Chetan

unread,
Jul 8, 2004, 6:25:43 AM7/8/04
to
We have a centralised network server where the PB
application & sybase o/c (12.5) are deployed & all files are
write protected. The users run the application deployed on
this server from their desktop. The problem is when ever
there is a change in the IP address of the database server
subsequent changes are to be made in the sql.ini file on the
deployed server. This takes few days to carry out the
changes since it involves some formalities. To avoid this,
Could the application while connecting to the database make
sybase client reads the customised sql.ini on the user
machine instead of the default path on the deployed server.
Sybase o/c is not deployed at the users machine. In short,
I want sybase to read the sql.ini from the user machine &
other stuff from the deployed server while connecting to the
database.

Thanks

Bruce Armstrong [TeamSybase]

unread,
Jul 8, 2004, 9:53:07 AM7/8/04
to
Are you asking this over in the sybase.public.ase.general section?
That's where a lot more people hang out that can address your
question. This section is for PowerBuilder connectivity. While that
does include folks using ASE, the ase.general section is going to be
composed exclusively of those types.

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

Two new 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 mutliple personalities and hears voices in his head, the contents
of this message do not necessarily represent his own views.

0 new messages