Giorgio,

What about using JDBC to connect? It looks like you could get a JDBC driver from pervasive and switch your datasource from ODBC to JDBC. Might be worth a try - you can download from here I think:

http://www.pervasive.com/developerzone/access_methods/jdbc.asp

Hope this helps...

Jason

On Wednesday, July 30, 2003, at 05:36 PM, Ferr� A&T - Giorgio Tassistro wrote:

Phil,
ok ... but how I use Pervasive.SQL 2000i ?

I developed other 100 taf applications in old Tango 2000.
I bought (last month) Witango 5 because It was full compatible with my
application.
Now, it's not more COMPATIBLE ?
If Pervasive don't make ODBC 3.0, what I do ?
But I am only Witango (Tango 2000) developer with this problem ?

Giorgio


----- Original Message ----- From: "Phil Wade" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, July 30, 2003 8:56 AM Subject: Witango-Talk: Using non ODBC 3 drivers with 5.0.1.062


We have had a lot of questions regarding ODBC drivers and I want clarify
what the situation is with the use of non ODBC 3.0 drivers with Witango
Server 5.0.1.062.


Put simply there are several layers and interface versions to ODBC. The
witango applications communicate with the ODBC Driver Manager. This is
the
library that presents our applications with a standard interface across
all
platforms. It is the ODBC driver manager that loads the ODBC driver for
your database. The Witango Server does not access the ODBC Database
Driver
directly, but through calls to the ODBC Driver Manager like this:


Witango ODBC3 ODBC ODBC3 ODBC ODBC3 --
Server <=======> Driver <=======> Database <=======> |DB|
Manager ODBC2 Driver ODBC2 --



Witango 5.0.1.062 is now what is known as a "pure ODBC 3.0 application"
which means that it is a 32-bit application that is compiled with 3.0
headers, calls ODBC 3.0 functions and expects ODBC 3.0 behavior for
features. This was necessary to fix issues with blob and clob data types
that are not supported in earlier versions of the ODBC interfaces.


What we have done in the 5.0.1.062 server is to make the server
communicate
with the ODBC Driver Manager using the 3.x specification. Depending on
how
well your ODBC Driver Manager is written the ODBC Driver Manager should
recognize that the ODBC database driver is using a version 2.x interface
and
translate the ODBC 3 calls from the Witango Server to ODBC 2.x calls to
the
ODBC database driver.

Witango ODBC3 ODBC ODBC2 ODBC ODBC2 --
Server <=======> Driver <=======> Database <=======>
|DB|
Manager Driver --

It will then return the results to the Witango Server packaged in an ODBC
3.0 structure.


You will need to test your ODBC Driver Manager and ODBC database driver to
verify if they work. Most drivers should continue to work without
modification if the ODBC Driver Manager does a good job of translating the
calls and the ODBC database driver implements the full ODBC 2.5 interface.


If you find that the ODBC driver you are using does not work, check with
your database vendor on if/when a ODBC 3.0 driver will be available or
whether a JDBC driver is available.


Incidentally ODBC 3.0 was released back in 1996 so it has been around for
a
while.

Phil



______________________________________________________________________ __
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf



_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf



--
____________________________________________________________________

Jason Pamental, President [EMAIL PROTECTED]

Bathysphere Digital Media Services, Inc. http://bathyspheredms.com
____________________________________________________________________


Tel: 401.490.6830      Fax: 401.490.6831
________________________________________


A North American Distributor for Witango (http://www.witango.us)


Rapid Web Application Development - XML Execution Engine


________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf

Reply via email to