MS Access interferes with our COM objects DDE traffic. Known problem?

P

Patrik Sj?gren

Hi,
We have a problem with access of a COM object using VBA from MS
Access.
It works fine within MS Word but Access seems to interfere with DDE
traffic.
First of all, our COM object is not a GUI object. All it contains is
around
20 methods that use BSTR to send and receive information, e.g:

virtual /* [helpstring][id] */ HRESULT STDMETHODCALLTYPE
PACSGetVersion(
/* [retval][out] */ BSTR *version) = 0;

The methods in the COM object in turn calls a corresponding DDE
function
of our applications to exchange information. The data returned through
the DDE interface is correct, according to the logs. However, when the
VBA-code is run in MS Access, the returned information from the DDE
call, in this case "PACS_version<1.4>", is replaced with "Error"
before arriving to our COM object. So, MS Access somehow corrupts the
information received via DDE to our COM object before it arrives. The
same VBA-code works fine when run from MS Word.
The problem seems to be that MS Access somehow interferes with DDE
communication, and in our case even replaces data.

Is this a known problem?
Is there any cure for it?

thanks/Patrik Sjögren
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

MS Access interferes in our COM object's DDE traffic 0
VBA to úse external COM object (difference between Word and Access VBA?) 1
VBA macro works in MS Word but not in MS Access 2000 (COM objects) 1
Com port samples on Access VBA 1
Word Mailmerge using DDE with Access problem 2
MS Access Database via DDE Not connecting 3
Problem with Upgrade MS Access 2003 to Access 2007 10
Need Project 2003 COM object but not Project 6

Top