Sign up using Facebook. You should be able to edit the ODBC data source or add a new data source. It doesn’t work in Win7 64bit. One way to see this is to manually create the ODBC entry on a bit system. Run the following command:
|Date Added:||11 November 2004|
|File Size:||11.5 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Any idea on how to make the connection show in the GUI?
Protect the ODBC Drivers
Can someone show inno-setup code that will work for both 32 and 64bit OS. Is there no one that can help me? For days, we tried to recreate the issue in our labs, but were unsuccessful. It doesn’t work in Win7 64bit. Our adaptive server anywhere 7.0 odbc for avoiding this problem was to isolate our installation of the Adaptive Server Anywhere ODBC driver, and “brand” it with our company name.
Since ODBC profiles are really nothing more than Registry entries, the technique for doing this is as follows:. Accroding to these articles, we can re-register the driver using regsvr32 or manually change Registry. However the ODBC connection works.
I am looking for sample inno-setup code to enter the ODBC entry in the registry. Sign adaptive server anywhere 7.0 odbc or log in Sign up using Google.
Wei Ding: Missing Sybase Adaptive Server Anywhere ODBC Driver
Newer Post Older Post Home. Solution 2 The second solution requires you to edit the registry: I’m using inno-setup to compile an install file. Recently, one of our client sites started reporting strange system errors with our software. One way to see this is to manually create the Servet entry on a bit system. I now need someone’s expert opinion. Since both software packages were written to use the “Adaptive Adaptive server anywhere 7.0 odbc Anywhere n.
I odbx based my current logic from the below post. Post as a guest Name. At a command prompt, navigate to the Pylon Anywhere installation directory for example, C: That gave us total control over the software, and protected us from getting overwritten by any other software setup routines.
When we finally opened a remote desktop sharing session to the individual user’s PC, we noticed that the ODBC driver files for SQL Anywhere were for a much older build of afaptive same version. Place the Adaptive Server Anywhere deployment drivers into a adaptive server anywhere 7.0 odbc location on the server or workstation.