Inventor 2014 64-bit breaks database connections.

[Anonymous]

1)  I get an error saying I need to add an attribute called PtrSafe to my Delcare statements.

Did that an things seem to move forward.

2) I access several different databases through my macros.

Connecting to Access via jet 4.0 throws an error.  Provider not found.

Weird thing is if I fire up 2011 I do not get this error.

Connecting to MAS 200 I get an error saying that the ODBC DSN contains an architecture mismatch between the   driver and the application.

Following up on the ODBC error it says something about the C:\Windows\SysWow64 folder.

I see no such folder on my 64 bit windows 7 machine.

What can I do to fix the issue?

[xiaodong_liang]

Hi,

this seems duplicated with the other thread:

http://forums.autodesk.com/t5/Autodesk-Inventor-Customization/MacroControlDefinition-does-not-work-i...

But I'd like to repeat:

MS provided new VBA which has 64bits version. Inventor 2014 uses it. So now VBA is also running within Inventor process (64bits). Have you tried in other VBA environment such as Excel, Word 2010? If it is reproducible, you would have to consult with MS how to connect Database in VBA. Appreciate if you could share the solution when you get any.

[Anonymous]

Not duplicated.  Related yes,

This thread is mainly about connecting to databases in Inventor 64 bit VBA 7 that use a 32 bit driver.

The short answer is that you cannot with out a 64 bit driver.

We upgraded this week from MS Office 2000 to MS Office 2013.

Running Excel VBA 7 64 bit as a test I can now connect to my database(s)

Inventor is another story.  New problems there.

The other thread is about VBA macros not running from an addin.

In that case it is the 32 bit specific code... say Windows API declarations that may be causing the failure. 

[ekinsb]

You're correct that in order to use the MS data access components in Inventor 2014 you need to have the 64-bit version of those components.  When you say Office 2013, I assume you actually mean Office 365.  We've discovered an issue with Office 365 where it installs the components in a way that they can only be used from within an Office application.  We're waiting for some clarification from Microsoft.

In the meantime a simple workaround is to install the component seperately from here:

http://www.microsoft.com/en-us/download/details.aspx?id=13255

---

@Anonymous wrote:

This thread is mainly about connecting to databases in Inventor 64 bit VBA 7 that use a 32 bit driver.

The short answer is that you cannot with out a 64 bit driver.

We upgraded this week from MS Office 2000 to MS Office 2013.

Running Excel VBA 7 64 bit as a test I can now connect to my database(s)

Inventor is another story.  New problems there.