why can i use myob Odbc direct driver v7my with windows 7, i have tried using the same odbc driver with XP and vista and it works fine.
please help me tnx.
If you're running a 64bit version of Windows, then you need to make sure you run the 32-bit version of the ODBC control panel to get access.
C:\Windows\SysWOW64\odbcad32.exe
However, need a bit more detail to find out if that's your problem.
Related
I have managed this in the past on two separate machines. Now one machine has lost the DSNs and I cannot for the life of me add them back.
Uninstalled all MariaDB exes and MariaDB ODBC drivers.
Installed latest MariDB 10.5 and latest 32-bit MariaDB ODBC 3.1 drivers 3.1.9 (26/6/20)
Using ODBCad64 I am informed I am not administrator when I am (but this is not a huge problem, and other answers point to Office causing this).
I want to use 32bit drivers with VFP9 anyway, so usually run ODBCad32.exe as administrator, go to System DSNs and Add...
I can add any of the listed drivers except the MariaDB ODBC 3.1 Driver, which just shows a thinking-about-it cursor for a few seconds, then nothing, rather than the dialogue to choose the data source.
This behaviour occurs on User DSNs as well. On a separate Win10 machine I correctly get the next dialogue "Create a new Data Source to MariaDB" wizard, which I have had in the past on the problem machine. The problem machine will be the production database server, and has worked perfectly in the past, before losing the DSNs.
The other machine is development and bizarrely can still connect to the production machine, even though I uninstalled and reinstalled everything there and haven't setup DSNs there, and cannot see any existing ones. The development machine connects to MariaDB 10.05 (correct, just installed that on the production machine 10 minutes ago) using DRIVER={MariaDB ODBC 3.1 Driver};TCPIP=1;SERVER=;UID=root;PWD=*******;PORT=4306 (there is an existing service on 3306).
So the Driver appears to be working remotely, but I cannot add DSNs to use ODBC locally. What I can do is (locally) send the complete SQL connection string from VFP i.e. a DSN-less connection.
Any ideas much appreciated!
OS: Microsoft Windows Server 2008 R2 Enterprise - 64-bit - En.Us
DBMS: Microsoft SQL Server 2008 R2 Standard - Windows - 64-bit - En.Us
ODBC Driver: Progress OpenEdge 10.2B - Windows - 32-bit - En.Us
I don't have the related ODBC Driver in 64-bit version.
Do I have options to connect, to the Progress Database, using Query, or Linked Server? If I have, what are my options?
Thank you all!!!
The Progress ODBC drivers can be downloaded from the Progress site. Log in with your ID on http://www.progress.com/esd/
Contact support if you can't find them.
There's also a product called "Pro2" replication that can "almost live" replicate from Progress to for instance SQL server if you have that demand. It might only be offered from 11.X and forward, I'm unsure about that.
https://www.progress.com/openedge/features/openedge-pro2/
If you were to download one of the 11x 64bit Client Access bundles, these will quite happily connect to a 32bit 10.2b database.
http://knowledgebase.progress.com/articles/Article/P88405
You do have options. Fundamentally, you can use our Multi-Tier ODBC Drivers for Progress (versions 6.x to 10.x) to connect a 64-Bit ODBC Compliant application to a 32-Bit Progress RDBMS. This 64-Bit client to 32-Bit server bridging is achieved as a result of the RDBMS-independent communications layer used by these drivers.
I am trying to install the correct Oracle drivers on my development machine. I'm creating an ASP.NET web site and every time I run I get an error saying that says "The provider is not compatible with the version of Oracle client". I have tried both 32-bit and 64-bit Oracle drivers but have still had no luck. Can someone lead me to a link for the drivers I need based on my specs?
I'm using Windows 8 64-bit. The database is Oracle 11.2.0.2.0 - 64 bit.
The ODAC112021Xcopy_x64.zip might give you the dll's and client you'll need. Take a look at this previous answer for more detail about deployment of the application.
I am trying to access an Omnis database on MacOSX using a c# .NET application on Windows 2008 64 bit.
This is a can of worms! There is no 64 bit driver for Omnis for Windows 2008 - I have tried the 32 bit one but the feedback from this site is that 64bit applications cannot access 32 bit ODBC drivers.
Other than exporting all the data does anyone have any suggestions, including products which may provide a solution here? Thanks Mike
We, at OpenLink Software have a Multi-tier ODBC to ODBC Bridge that might help...
You could configure it like this -
Windows Client --
64bit ODBC Application
64bit OpenLink Generic ODBC Driver (Multi-tier client)
32bit OpenLink Request Broker (Multi-tier server)
32bit ODBC Agent (Multi-tier server)
32bit Omnis ODBC Driver + 32bit configured DSN
Mac Server --
Omnis
So, basically, the ODBC to ODBC Bridge is simply being used to bridge from 64bit client components to 32bit server components - all on the same machine...
Whilst this may not be the most graceful solution - in the absence of a dedicated 64bit Omnis ODBC Driver it may be all you have available to you...
You've got to use the 32 bit ODBC manager in windows. Via a command prompt, go to
%system%\syswow64
and launch odbcad32.exe
After that has come up, you can edit your odbc entries as you expect and the 32 bit Omnis application will be able to see them.
You need to use this driver in conjunction with the 32-bit ODBC Administrator, the 32bit ODBC Administrator can be found at:
C:\Windows\SysWOW64\ODBCAD32.exe
Right click the link in Start/Administrator Tools/DataSources (ODBC) and change the path to:
%windir%\SysWOW64\odbcad32.exe
Navigate to 'regedit' with the 'RUN' command, then locate 'HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Omnis ODBC Driver'
Modify the line 'Driver' to
'%windir%\Windows\SysWOW64\Omnis\omodbc32.dll'
Modify the line 'Setup' to
'%windir%\Windows\SysWOW64\Omnis\omodbc32.dll'
Hi i have an application developed on XP with Text ODBC drivers. But when i deployed on Win 7 with office 2007, i have connection issues.
<add key="SQLConnection.TextConnectionString" value="Driver={Microsoft Text Driver (*.txt; *.csv)};Dbq=c:\Data\;Extensions=asc,csv,tab,txt;Persist Security Info=False" />
ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
i have googled every solutions like installing the following
http://blogs.msdn.com/b/sqlblog/archive/2009/12/29/how-to-connect-to-file-based-data-sources-microsoft-access-microsoft-excel-and-text-files-from-a-64-bit-application.aspx
Microsoft Access Database Engine 2010 Redistributable (32-bit)
2007 Office System Driver: Data Connectivity Components
after all of those, in my datasources(ODBC), it still only shows "SQL native client/SQL server/SQL server native client"
in the C:\Windows\SysWOW64\odbcad32.exe
i can see all the x32 drivers, but how can i modify my connection strings to access 32-bit Microsoft Text Drivers or are there any alternative solutions?
Thanks
I'm pretty sure it'll work automatically (even on a 64-bit machine) as long as the executing process is 32-bit.
Try recompiling to target x86 specifically.
You need the 64-bit Microsoft Access Database Engine 2010 Redistributable
http://www.microsoft.com/downloads/details.aspx?familyid=C06B8369-60DD-4B64-A44B-84B371EDE16D&displaylang=en
Then try
Microsoft Access Text Driver (*.txt, *.csv)
for the driver name.
AFAIK, all 64-bit ODBC drivers from the Microsoft Access Database Engine 2010 64-bit Redistributable have slightly changed their driver names, I guess to differentiate them from their 32-bit counterparts.
I had this exact problem and the recompiling to target x86 specifically worked! Note that in order to do this I had to specify the Target CPU in the advanced compiler setting dialog - Project Menu> Properties> Compile tab> Advanced Compile Options button.
Before finding this forum entry I did install the Microsoft Access Database Engine 2010 Redistributable (32-bit) but I don't know if that had any affect on this issue.
As mentioned above, when the executing process is 32-bit (in this case compiling against x86 makes the app 32-bit specific) the application will use the drivers from C:\Windows\SysWOW64\odbcad32.exe.
Thanks Cameron.
We were doing this from ASP.Net and got it working on Windows 2012 just by moving the one site into a separate app pool that had "32-bit Enabled" turned on in the advanced settings for the App Pool.
A lot of people seem desperate here, I want to offer a few solutions. But, first I want to highlight what a dated proprietary trash idea from the 90s this is.
Use Unix ODBC to host the text file from Linux which the docs (seem to) claim to support an implementation of the Microsoft text driver
A better option would be of course to import the CSV into PostgreSQL.
I would suggest just doing this with \COPY and dropping the notion of a CSV.
You can maintain the CSV with PostgreSQL acting as a server with the Foreign Data Wrapper (file_fdw).
If you don't want to run an RDBMS, the modern way would be to use SQLite. This is a great idea if you don't need the server/client model.
The ODBC->text interface is especially insane, because ODBC doesn't define configuration beyond connection (so I assume there are lots of assumptions there).