Has anyone gotten a error message box when launching an Access application that states "There was a problem sending the communication to the program"? We just starting getting this message when we converted to Windows 7 and Office 2010. The applications previously had not been getting it. Almost, if not all, Access applications are seeing this error come up on launch. It does not stop the program from launching, but it does annoy and confuse the users.
Ok, I used a recommendation from Microsoft and ran this test, and it came up false, pointing to no broken reference.
The BrokenReference property
The Application object for Access has a BrokenReference property that tells you if any references are broken. To check the BrokenReference property, follow these steps:
Open an Access database.
Press ALT+F11 to open the Visual Basic Editor.
Press CTRL+G to open the Immediate window.
In the Immediate window, type the following command, and then press ENTER:
Notice that the BrokenReference property for the Application object returns True if there are missing references. Otherwise, the BrokenReference property returns False.
If you open on a machine with the full version of access and press control break while the error message is up, that should give you a general idea of where in the code execution the error occurs (assuming it is a code generated message). Your original message indicates there is an error trap somewhere that is doing it's job (which is why the app continues to work) and finding that trap would be beneficial.
It could also refer to a number of possibilities that actually relate to the message (I know that the error messages in Access seldom relate to the actual problem, but sometimes they do):
1) Does your app use external data connections (Access mdb, SQL, ODBC, other sources)?
2) Does your app use automation (to connect with Excel, Outlook, etc.)?
Also, perhaps open the app in bypass (so that nothing actually runs) and try opening each linked table one at a time (to see if there is a specific culprit). Same thing for each query (in case there are pass thrus of functions that pull data).
Did you convert from Access 2007, 2003, 2000 or 97?
Is there code that references API's that are perhaps out of date in Windows 7?
Is there a network timeout issue? Sometimes, the initial connection takes too long, tripping an error, but then it works, because the connection finally opens.