SQL Anywhere Client Application Deployment

Darryl Booth

unread,

Feb 5, 1998, 3:00:00 AM2/5/98

to

As a Corporate Application Partner (CAP), we're just about ready to begin
distributing our software with SQL Anywhere 5.5.0.3. I'm charged with
creating the installation process.

I've downloaded and studied the document(s) titled Sybase SQL Anywhere
Client Application Deployment. This document outlines the files required
for a SQL Anywhere Client isntallation.

However, it doesn't speak to changes to the registry (excepting those
posted for ODBC access) nor does it mention changes to the autoexec.bat.

Where can I go to get an understanding of the changes required to the
registry for a SQL Anywhere Client Installation?

Or, Perhaps the ODBC entries are the only entries required.

Thank you inadvance.

-Darryl

Bjorn Andre Lie

unread,

Feb 6, 1998, 3:00:00 AM2/6/98

to

Hi,

When you have installed the SQL AnyWhere Client you must run the ODBC
administrator and set it up to run as a client giving the name of the
server and network connection parameters. When your application starts
it will start the client engine and look for the server throug the
network parameter specified in the ODBC setup. There is no need to do
any changes in the registry or any other files.

Regards
Bjorn Andre

Chris Johnson

unread,

Feb 6, 1998, 3:00:00 AM2/6/98

to

True, but if you are running an unattended install, using the ODBC
administrator is not an option. You can simulate the effects of this tool
via entries in the registry. I think this is what Darryl was referring to.

Autoexec.bat changes -- it is good to make your PATH include the directory
where the SQL Anywhere files are installed. Maybe not necessary, but be
safe.

Registry changes -- the easiest way to see what you need to set up is to
use the ODBC administrator on a development machine, then look at the
registry and see what happened -- the changes will be under
XXX\Software\ODBC\ODBC.INI\(name of your data source) -- the "XXX" part can
be either HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE, depending on whether
this is a user or system DSN.

Regards
-- Chris

Bjorn Andre Lie <Bjorn.A...@LightWare.no> wrote in article
<34DAC7...@LightWare.no>...

David Lance Wolf

unread,

Feb 6, 1998, 3:00:00 AM2/6/98

to

My client uses InstallShield and a product called visual test to do these
installs. Visual test is a GUI map tool, that actually brings up the ODBC
Administrator, and clicks the buttons, fill in the fields, etc. So they dont
need to mess with the registry settings. Works like a champ. We actually
install SQLA by having VisualTest run the SQLA setup, and click all the right
buttons.

I can get more info from the client if your interested.

Dave Wolf
Sybase Professional Services

Darryl Booth

unread,

Feb 7, 1998, 3:00:00 AM2/7/98

to

I am interested in your client's VisualTest Tool. However, my understanding
of InstallShield is that the ODBC settings and BDE (Borland Database Engine)
settings should be OK. At this point, I'm mainly concerned in any special
entries that are necessary to launch dbclient, isql, and Sybase Central on
the target system.

I found SETUP.INF on the CD-ROM and found no references to registry entries
leading me to conclude that no special entries are required to launch the
utilities listed above.

Do you disagree?

-Darryl

David Lance Wolf wrote in message <34DB2F62...@sybase.com>...

Andy Tynan

unread,

Feb 8, 1998, 3:00:00 AM2/8/98

to

Darryl

If you do an installation of SQL Anywhere and select the
"No I want to fiddle with my own setup files later"
option at the end of the setup, it will write the changes to a file
called <something>.ENV. Anyway, it will tell you.

And if you are *still* stuck, I can give you more stuff, because I had
to do this last year.
In fact I had to write an IDAPI.CFG editor DLL as well, and this was a
lot harder to get the information for (Borland were somewhat reticent
for some reason).

Installshield is not the most enjoyable environment I've worked with,
when it comes to installations which want to do more than just copy
files.

Have fun,

Andy Tynan
Database Manager
SIMS Education Services Ltd.

Eric Silver

unread,

Feb 9, 1998, 3:00:00 AM2/9/98

to

Darryl,
I have just completed a full setup utilizing either a server based ODBC
setup or a standalone ODBC setup. I have as well developed a Windows NT and
Novell server Installation program both using InstallShield.
It does not take must to setup the ODBC in either situation. If you need me
to provide example source code you can contact me at B...@ols-inc.com. The
code is written in a modular fashion, so if you have not figured it out
please feel free to contact me.
B Abney
B&E Technologies Inc.
WWW.BETechno.com

Andy Tynan wrote in message <34DE45A9...@dial.pipex.com>...