[AccessD] How to troubleshoot

Darryl Collins darryl at whittleconsulting.com.au
Wed Aug 24 22:49:28 CDT 2011


John, probably way off target here but I know that if you have the COM
Add-in "Send to Bluetooth" available it can cause this error, at least in a
Windows 7 2007/2010 environment, turning off the addin fixes the problem.
Now I have no idea if that impacts the runtime or not. Or worse, it is
causing the problem, how on earth would you fix it in the runtime :-/

Anyway, just putting some ideas out there.


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Thursday, 25 August 2011 12:19 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] How to troubleshoot

Any clue how to troubleshoot "Access has stopped working" in the 2007
runtime?  I have a version 
that works just fine, and another app works just fine but the latest version
just immediately closes 
giving that error message.  "A problem sending a command to the program".

-- 
John W. Colby
www.ColbyConsulting.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list