scenenoob.blogg.se - Works in access runtime 2010 but not in 2013

#Works in access runtime 2010 but not in 2013 drivers#
#Works in access runtime 2010 but not in 2013 driver#
#Works in access runtime 2010 but not in 2013 upgrade#

Registry path: HKEY_LOCAL_MACHINE\Software\Microsoft\Office\14.0\Outlook

You can determine the bitness of Access (or the whole of Office, really) from this registry key (see ):.

In other words, if you have 32-bit Access you need the 32-bit Oracle Client, and if you have 64-bit Access you need the 64-bit Oracle Client.

The bitness of the Oracle client must match the bitness of Access, not the bitness of Windows.

I learned from various places to make it work was this:

This had previously been working on my old computer running Access 2007 and Windows XP, but my new computer has Access 2010 and Windows 7. I had a similar problem over the last 2 days getting MS Access 2010 to access an Oracle database.

Have you been able to test the connection to Oracle successfully by setting up a DSN in the ODBC Administrator? Search the file for the error number or just the word error and see what you find. Launch Access and try to connect to Oracle, then turn off the tracing and open the resulting SQL.log file. Back in the ODBC Administrator, you could try turning on ODBC tracing to see if you can find more information on the error. What is the bitness of Windows and Access and the Oracle client tools on these 2 PCs (x86 or 圆4)?ĥ.

#Works in access runtime 2010 but not in 2013 driver#

What version of Oracle are you connecting to and what Oracle driver version are you using?Ĥ. If you need to launch the 32bit ODBC administrator on a 64bit OS, launch it from c:\windows\syswow64\odbcad32.exe.ģ.

#Works in access runtime 2010 but not in 2013 drivers#

Tools > Data Sources (ODBC)) and selecting the drivers tab. Does the driver version match that of the working PC? You can verify this by going to the ODBC administrator (Start > Control Panel > Administrative Have you installed the Oracle ODBC driver on this machine?Ģ. On the Oracle setup on this second machine.ġ. Will this impact which Office IĪs for the VB problems, so far I have found two compile errors, both "can't find project or library." Specifically, they bring up "fd As FileDialog" and "Left" (after "Select Case") in the debugger.I would first verify that both machines have the same service packs applied for Windows and Office to eliminate concerns in that area. I'm running Windows 7 on the desktop and am not inclined at this point to upgrade. If I do upgrade, what changes am I going to need to make to the code? It's been years since I did the code, so I'm really rusty on this. Panel and tried the Compact and Repair Database in Access, although it never gave me any dialog for that, so I don't know if it did anything. I have repaired my 2010 Office via the Control The database also seems to be looking for something when it opens the form I'm using, quickly flashing a dialog box that it hasn't before (so fast that I can't read it), but it never brings up an actual error.

#Works in access runtime 2010 but not in 2013 upgrade#

Never had them before this point.Ĭan I assume this is related to Office 365? Is there anything I can do to make these programs work together with the same database, and get my VB to work, or do I now need to upgrade the Office on my desktop? Should've thought that through first! I didn't do much with it on my Surface, but since then, when I open it in Access 2010 back on my desktop, I'm getting "compile errors" with the Visual Basic.

I recently bought a Surface and subscribed to Office 365, with which I opened this database - through a home network, but also hope to use via cloud I have an Access db which I wrote with Access 2010 and still use with that software on my desktop computer.