P
Patrik Sj?gren
Hi,
We have a COM object, which in turn use DDE to communicate with
another application of ours. Access to this COM object works fine
from C++, Visual Basic applications, VBS and VBA from MS Word.
But the the same VBA code that works in Word fails in MS Access.
Our COM object is not a GUI object. All it contains is
around 20 methods that use BSTR to send and receive information.
The debug version of the COM object we've written to investigate
this problem pops up a message box just after receiving the string.
The message box says it has received the string "Error" while our
DDE log shows that we have sent "Pacs_version<1.4>". So, somewhere
on the way MS Access replaces the data sent via DDE before it arrives
to our DLL/COM object. Or, MS Access somehow prevents the DDE call
to return.
I get the same result in MS Word when I place a breakpoint in our
application to halt the DDE call from the DLL. This triggers a timout
in MS Word/VB that releases after about 10-15 seconds and the result is
the same as in MS Access (with the difference that it returns immediately
in MS Access). I.e. the returned string is "Error".
Could it be some initiation of DDE that needs to be done in MS Access?
thanks/Patrik Sjögren, Sectra
We have a COM object, which in turn use DDE to communicate with
another application of ours. Access to this COM object works fine
from C++, Visual Basic applications, VBS and VBA from MS Word.
But the the same VBA code that works in Word fails in MS Access.
Our COM object is not a GUI object. All it contains is
around 20 methods that use BSTR to send and receive information.
The debug version of the COM object we've written to investigate
this problem pops up a message box just after receiving the string.
The message box says it has received the string "Error" while our
DDE log shows that we have sent "Pacs_version<1.4>". So, somewhere
on the way MS Access replaces the data sent via DDE before it arrives
to our DLL/COM object. Or, MS Access somehow prevents the DDE call
to return.
I get the same result in MS Word when I place a breakpoint in our
application to halt the DDE call from the DLL. This triggers a timout
in MS Word/VB that releases after about 10-15 seconds and the result is
the same as in MS Access (with the difference that it returns immediately
in MS Access). I.e. the returned string is "Error".
Could it be some initiation of DDE that needs to be done in MS Access?
thanks/Patrik Sjögren, Sectra