Watcom ODBC Driver

[mark...@gmail.com]

I've been given a really old VB application and while the front end
can be redesigned, the database is a Sybase 5.5 file and needs
porting. In fact it needs a Watcom ODBC 5.5 driver?

Having looked around on the current product list, there have been
*lots* of product revisions of the database engine and so it's not
suprising that the current Sybase SQL Anywhere 10 Developer Suite
cannot access such an old database (also stated in the discontinued
support notice
- http://www.sybase.com/detail?id=1013108)

Thus, the question is - where can I get a copy of the old Win32 ODBC
driver that can connect to this version. the application's
documentation refers to WOD50T.DLL v5.05.05.2817 as the recommended
driver.

thanks.

markm

[Dmitri]

<mark...@gmail.com> wrote:

> I've been given a really old VB application and while the front end
> can be redesigned, the database is a Sybase 5.5 file and needs
> porting. In fact it needs a Watcom ODBC 5.5 driver?

If you have a 5.5 server, you (most likely) have a driver. If you have no
server, the driver is useless to you.

Dmitri.

[Frank Ploessel]

Markm,

You can access the database file with a version 9 engine. In my
experience, this can be really slow, but it works. I would recommend to
re-load the database to an empty database file created with the version
that you use as the engine. Is this an in-house developed application or
one bought? In the latter case, I would contact the vendor.

By the way, I have a setup CD from our application available from 8 years
ago with a version 5.5.0.4 driver. If you are properly licensed, I could
send that driver to you.

Frank

[Volker Barth]

In addition to what Dmitri wrote:

AFAIK, all versions from SQL Aynwhere 5.5 to 9.x are able to start a 5.5
database so you could get along with newer versions (with some restrictions
to network clients).
FWIW, the main 5.5 driver file is called wod50t.dll (for Windows 32 bit).

HTH
Volker

"Dmitri" <NOdi...@mail15.com> wrote in news:47cbc468$1@forums-1-dub...

[mark...@gmail.com]

Hi guys,

To further answer some of your questions....

The application is VB5, written inhouse and no suprise, the source
code has been lost.
I've been tasked with redeveloping the software to streamline the
processing and bringing it into the 21st Centrury ;-)

When the application does spin up a separate window turns up stating
the following.... not sure if this is something done by sybase or the
app.

Sybase SQL Anywhere Database Engine Version 5.5.05 Build #2817
Copyright by Sybase, Inc., and its subsidiaries, 1988, 1999.
All rights reserved. Sybase is a trademark of Sybase, Inc.

The application only came as one install - it actually copies over
only part of the driver though. Checking the ODBC32 Admin screens
displays the driver info as WOD50T.DLL v5.05.05.2817 but I cannot
reconfigure the connection (DSN) the application installed - the
ODBC32 Admin screen just bails out with an error:

Driver's ConfigDSN, ConfigDriver..... Component not found in the
registry.

This error has no bearing on the application since it works
regardless.

There is no "server install" for the application. There is a local
".db" file that I know is the where the database exists.
I am guessing that the application might be doing a direct access to
the file rather than any engine?

To this effect, I have no clue as to if I have a licence or how to get
one since support for this version seems to be dropped or unavailable
for download. I only really need to be able to port the database to a
newer version that is maintainable.

many thanks!!!
mark

[Dmitri]

<mark...@gmail.com> wrote:

> Sybase SQL Anywhere Database Engine Version 5.5.05 Build #2817
> Copyright by Sybase, Inc., and its subsidiaries, 1988, 1999.
> All rights reserved. Sybase is a trademark of Sybase, Inc.

In fact it is a database engine in its glory :) (dbeng50.exe - a single-user
SA 5.5 variety).

> The application only came as one install - it actually copies over
> only part of the driver though. Checking the ODBC32 Admin screens
> displays the driver info as WOD50T.DLL v5.05.05.2817 but I cannot
> reconfigure the connection (DSN) the application installed - the
> ODBC32 Admin screen just bails out with an error:

SA 5.5 driver not properly configured or setup DLL went missing... not sure
which one exactly as I haven't used V5.5 for 4 odd years.

> I am guessing that the application might be doing a direct access to
> the file rather than any engine?

No, because it is impossible.

> I only really need to be able to port the database to a
> newer version that is maintainable.

In short, you can start your database on any ASA version up to 9.
Alternatively, you can migrate your database to the SA 10.

Dmitri.

[mark...@gmail.com]

> > I only really need to be able to port the database to a
> > newer version that is maintainable.
>
> In short, you can start your database on any ASA version up to 9.
> Alternatively, you can migrate your database to the SA 10.
>

Dimitri

Downloaded and installed the ASA developer toolkit v9 and managed to
get fully connectivity under that ODBC driver from my .NET test
harness.

Will now look at upgrading/porting the data over.

for now - thanks very much!

mark

[Stephen Rice]

As other have impled you probably have everything you need. The issue sound
like an incomplete odbc registry setup.

If you don't want to embark on the road to v10 (though I strongly recommend
you do) you need to verify you can find the files:

dbeng50t.exe
wod50t.dll
wl50ent.dll

The ODBC section of the registry contains two sets of entries, one which
point to the driver used by applications making connections (this one is
setup ok since you application works) and one which is used to manage data
sources (this one is probably broken/not there)

The minimum you need to do is make manual entries on your development
machine that match what is on a working machine.

If you want to setup the datasource to be managed through the odbc
administrator (odbcad32.exe) you need registry entries that resemble:

[HKEY_LOCAL_MACHINE]
[SOFTWARE]
[ODBC]
[ODBC.INI]
[mydsn]
driver=c:\sa5\win32\wod50t.dll
uid=dba
pwd=sql
[ODBC Data Sources]
mydsb=SQL Anywhere 5
[ODBCINST.INI]
[SQL Anywhere 5]
Driver=c:\sa5\win32\wod50t.dll
Setup=c:\sa5\win32\wod50t.dll
[ODBC Drivers]
SQL Anywhere 5=Installed

If this was a 16bit app then check out http://www.sybase.com/detail?id=44477
--
/steve
Stephen Rice
Sybase iAnywhere

<mark...@gmail.com> wrote in message
news:14ebb5f6-836e-4874...@i12g2000prf.googlegroups.com...