Hello!

We are converting our web database from MS Access to Sybase.  I would like
to use Jet to access the new Sybase database for some operations.  I have
NO idea how to do this.  Does anyone have any suggestions of where to find
info?

Basically, I'd like to preserve as much of the code as possible from the
previous version (VB4.0 using Jet --> MS Access) to access the new Sybase
database.

Any suggestions?

Thanks for your help!!!

Gina

Gina,

We recently finished a product that uses Jet 2.5 and can operate on data
hosted in a Jet database, SQL Server (very similar to Sybase), or
Oracle.  We could probably do Sybase as well; we haven't had the need
yet.

We did this by using an MS Access database and attached tables.  The
application ships with three MS Access .MDB files:

  - The main data file which can be placed anywhere on the client's
network
  - A local data file which is stored on each user's hard drive
  - The "translation" database which attaches all of the tables from the
other two and contains all queries used by the system.  Each user gets a
copy of this translation database and the program allows them to refresh
the attachments to point to the main data file (somewhere on the
network).

As packaged, the program will run, but since the main data is stored in
an MS Access database, performance is somewhat sluggish.

When we have a client who has (or wants) SQL Server, we build the
database in SQL Server and then just refresh the attachments in the
"translation" database to point to the SQL Server tables (through
ODBC).  Using SQL Pass-Through, we still get the benefit of
client/server processing.

For your conversion, you should be able to create the necessary tables
in Sybase, and then just attach to them from your existing MS Access
database.  Since you can rename attached tables at the MS Access end,
you don't need to worry about the names in Sybase.  That is, if your
program currently uses an Access table called MyTable, but in Sybase
it's going to be called tbl_MyTable, you can attach to it and just
rename it back to MyTable (in the Access database) after attaching.  You
shouldn't have to change a single line of code because all of your table
names will be the same.  To the VB application, it will look as if
nothing has changed!

Attaching tables to a Jet database like this is actually the recommended
method for accessing "external" data, as Microsoft calls it.  If you
have the Professional Edition (or Enterprise) of VB, look at Chapter 7
of the Guide to Data Access Objects section of the Professional Features
guide.

If you would like more info, drop me a line.  I hope this helps!

Michael deFreitas
Whistler Computing, LLC

Set up an ODBC data source name in your Control Panel - ODBC. Then in
access, attach table to that ODBC source.