Access Crashes When Connecting to DSN

[mkaeser]

Hello all,

I am connecting Access to QuickBooks with the QODBC. I tried to do this in MS Access 2010 with Windows 7 and it worked fine. Then I tried it on a new computer with MS Access 2013 and Windows 7. Now, when the VBA gets to the line:

oConnection .Open "DSN=Quickbooks Data;OLE DB Services=-2"

It crashes. No message, other than the generic "Access has stopped working" message. I am using ADO for the oConnection. I am not sure what the problem is or how to diagnose it. I have used an ADO connection to connect to Excel, and that worked fine, so my guess is it have something to do with the DSN connection?

 

[Rx_]

It is a known issue with Quickbook's driver. Evidently Quickbooks has enough business they don't care about loosing market share.

At this link, the person appeared to spend hours (if not days) discussing the issue with a senior Quickbook tech. They also did a few things that made it "less-worse". The internet is full of places that had the problem switching up to Access 2013.

It is a Memory leak issue. This site has someone who spent months and found a 3rd party solution:
http://stackoverflow.com/questions/...-out-of-memory-error-in-quickbooks-enterprise

Would you please share if your Access 2013 has SP1 (or other updates) installed? There were some profound problems before SP1 arrived.

Microsoft Office Version	Service Pack	Size (MB)	Download
Office 20131	SP1	643.6	32-bit
SP1	                 774.0	64-bit2
Office 2010  	SP2	 638.2	32-bit
SP2	     730.4	    64-bit2
Office 2007	SP3	351.0	32-bit
Office 2003	SP3	117.7	32-bit
Office XP	SP3	57.5	32-bit
Office 2000	ink well and parchment replaces the chisel and hammer

 

[HairyArse]

I'm a bit late to the party on this one but I had the exact same issue. The way around it is to establish the link between your DB and Quickbooks using the QODBC setup wizard rather than by using a DSN.