Yes, well, I have a drive with my old OS and applications while I'm migrating
another to the new OS. You don't know all the hiccups and incompatibilities
until you give it a shot.
Installing Java is not a problem. I expected that ODBC would be natively
supported by the OS as it (sorta) was
Roland,
Could you confirm which version of the Studio were and are now using?
I ask because the Witango 6.0 Studio and TeraScribe 6.1 don't support ODBC,
only JDBC.
Also, the ODBC subsystem was somewhat deprecated in 10.6 and needed to be
installed manually. This is probably the case in 10.7
On Jul 30, 2011, at 12:33 PM, Robert Shubert wrote:
Roland,
Could you confirm which version of the Studio were and are now using?
6.0.7
I ask because the Witango 6.0 Studio and TeraScribe 6.1 don't support ODBC,
only JDBC.
really? It has New data sources: ODBC and JDBC.
Also, the ODBC
Roland,
The setup in Witango 6.0 + on OS X is that the Studio uses JDBC to introspect
the database (to load it into the Studio Database tab for drag and drop).
If you setup a Witango Data Source under the JDBC section, then the Studio will
create TAFs that expect to use JDBC on the server,
very helpful and a little hopeful.
The fact that neither JDBC nor ODBC options can be used to create a DSN tells
me that the JDBC drivers are hosed, also.
On Jul 30, 2011, at 1:12 PM, Robert Shubert wrote:
Roland,
The setup in Witango 6.0 + on OS X is that the Studio uses JDBC to introspect
ok, have jdbc running.
Are you telling me that I can create a datasource using the ODBC option, but
connecting to the dev database using the JDBC driver, which will then on the
production server find an ODBC DSN of the same name and use it? This is
sounding possible.
On Jul 30, 2011, at
This was successful.
Created a DSN using JDBC on dev machine with the same name as the ODBC on the
production server.
dev machine is hitting localhost via jdbc and production is hitting same name
database on production machine with ODBC.
Saveas version 5.5 because production server is still on
