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 5.5. made a simple test.taf using a builder. It worked with one hitch. The prev/next button didn't happen, but rather showed the code on the screen. Likely a typo somewhere in the builder.
On Jul 30, 2011, at 2:55 PM, Roland Dumas wrote: > 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 1:12 PM, Robert Shubert wrote: > >> 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, however, if you >> setup a Witango Data Source under the ODBC section, then the TAFs will look >> for ODBC DSNs when executed by the server. >> >> In this way, the OS X Studio can use JDBC to load the database, but you can >> still use ODBC on the server. >> >> Starting in 10.6 Apple has mostly dropped support for ODBC. I suspect this >> trend continued in 10.7. The iODBC subsystem is still present, but the >> manager is removed, JAVA support is non-existent and I'm not sure how well >> they are keeping up the functionality in Cocoa. I've tested with OpenLink on >> 10.6 and found that product to be a good solution. >> >> As things stand right now, Apple is neither supporting ODBC nor JDBC/Java, >> so database connectivity is being left out in the cold. Java 7 may resolve >> the JDBC issues and there's a good chance that if it does, we'll standardize >> on Java 7 & JDBC for connectivity support on OSX. >> >> I may also build in native connectors to Oracle (OCI), MSSQL (FreeTDS) and >> FileMaker (FMXML) but there are no immediate plans to do so. >> >> Robert >> >> >> -----Original Message----- >> From: Roland Dumas [mailto:radu...@mac.com] >> Sent: Saturday, July 30, 2011 3:48 PM >> To: Witango-Talk@witango.com >> Subject: Re: Witango-Talk: MacOS 10.7 ODBC >> >> >> 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 subsystem was somewhat deprecated in 10.6 and needed to be >>> installed manually. This is probably the case in 10.7 as well, but I >>> haven't tested it. Checkout KB: http://support.apple.com/kb/DL895 >> >> It was running prior to 10.6 and wasn't harmed when I upgraded to 10.7. It's >> completely hosed by upgrading to 10.7 >> >>> >>> The Server should still access the iodbc subsystem and DSNs, but driver >>> loading may be different. Also note that Lion is much more interested in >>> running in 64-bit, and you may be having issues with bitness and/or paths. >> >> I can't tell what it killed and what it just doesn't work with. On a support >> call to apple and getting passed around. The "enterprise" support people >> answer the question with "What is ODBC?" which tells me it might be hosed >> for good. Converting applications from ODBC to JDBC will be a significant >> project. >> >>> >>> Robert >>> >>> >>> -----Original Message----- >>> From: Roland Dumas [mailto:radu...@mac.com] >>> Sent: Saturday, July 30, 2011 3:04 PM >>> To: Witango-Talk@witango.com >>> Subject: Re: Witango-Talk: MacOS 10.7 ODBC >>> >>> The existing DSNs don't show up in the studio, to I went to re-create, but >>> there are no drivers. I go to look in the regular apple ODBC admin utility, >>> and it's nowhere to be found. I find open link iodbc manager, and it has >>> the drivers and DSNs listed, but they all fail when tested. Errors are >>> "specified driver could not be found" and "no such file or directory" >>> >>> So I figured the installation of 10.7 hosed up ODBC. Looking for hints how >>> to repair, reinstall, etc. >>> >>> >>> On Jul 30, 2011, at 9:27 AM, Robert Shubert wrote: >>> >>>> Roland, >>>> >>>> Could you clarify that you are looking for ODBC in the Studio? And also, >>>> which version of the Studio and/or Server are you running? >>>> >>>> Robert >>>> >>>> -----Original Message----- >>>> From: Roland Dumas [mailto:radu...@mac.com] >>>> Sent: Saturday, July 30, 2011 9:40 AM >>>> To: Witango-Talk@witango.com >>>> Subject: Re: Witango-Talk: MacOS 10.7 ODBC >>>> >>>> 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 previously. the upgrade wiped >>>> everything out. wondering what the right protocol is to re-install. >>>> _________________________ >>>> >>>> >>>> >>>> >>>> On Jul 30, 2011, at 12:42 AM, Wayne Irvine wrote: >>>> >>>>> Robert made an announcement recently about not supporting Lion yet. That >>>>> said, I installed 10.7 and Lion on what of my machines that already had >>>>> TeraScribe installed. I also installed Java (came up as an option when I >>>>> went to run a Java app). >>>>> >>>>> TeraScribe runs fine on this. >>>>> >>>>> Wayne Irvine >>>>> >>>>> On 30/07/2011, at 3:18 PM, Roland Dumas wrote: >>>>> >>>>>> >>>>>> upgraded to 10.7 and installed Witango dev studio. ODBC seems missing in >>>>>> this OS release. Anyone know the proper way to install/revive? >>>>>> >>>>>> >>>>>> ---------------------------------------- >>>>>> >>>>>> To unsubscribe from this list, please send an email to >>>>>> lists...@witango.com with "unsubscribe witango-talk" in the body. >>>>>> >>>>> >>>>> >>>>> >>>>> ---------------------------------------- >>>>> >>>>> To unsubscribe from this list, please send an email to >>>>> lists...@witango.com with "unsubscribe witango-talk" in the body. >>>>> >>>> >>>> >>>> >>>> ---------------------------------------- >>>> >>>> To unsubscribe from this list, please send an email to >>>> lists...@witango.com with "unsubscribe witango-talk" in the body. >>>> >>>> >>>> >>>> ---------------------------------------- >>>> >>>> To unsubscribe from this list, please send an email to >>>> lists...@witango.com with "unsubscribe witango-talk" in the body. >>>> >>> >>> >>> >>> ---------------------------------------- >>> >>> To unsubscribe from this list, please send an email to lists...@witango.com >>> with "unsubscribe witango-talk" in the body. >>> >>> >>> >>> ---------------------------------------- >>> >>> To unsubscribe from this list, please send an email to lists...@witango.com >>> with "unsubscribe witango-talk" in the body. >>> >> >> >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. >> >> >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to lists...@witango.com >> with "unsubscribe witango-talk" in the body. >> > > > > ---------------------------------------- > > To unsubscribe from this list, please send an email to lists...@witango.com > with "unsubscribe witango-talk" in the body. > ---------------------------------------- To unsubscribe from this list, please send an email to lists...@witango.com with "unsubscribe witango-talk" in the body.
