J
Jeff Brush
Hello all...
I've been getting a DDE link up between an Excel spreadsheet and a C program
that I'm working on, and I have many parts of it working fine. In
particular, I have a CommandButton, and in the code for that button, I can
successfully do a DDEInitiate() and then a DDERequest(), all works fine.
The problem is, I have an event in the spreadsheet that I want to add some
DDE functionality to. I can trap the event just fine with a
Worksheet_Change() and do all the Excel-side stuff ok, but when I call the
subroutine with the DDEInitiate() call in it, the C app never gets the
WM_DDE_INITIATE message. Here's the bizarre part - in the VB editor in
debug mode, I can trigger that subroutine and step through it, and
DDEInitiate sends the message to my C app, but when that subroutine is
called as a result of my trapped event, the message doesn't get through.
Any ideas??
Thanks!
-- Jeff Brush
I've been getting a DDE link up between an Excel spreadsheet and a C program
that I'm working on, and I have many parts of it working fine. In
particular, I have a CommandButton, and in the code for that button, I can
successfully do a DDEInitiate() and then a DDERequest(), all works fine.
The problem is, I have an event in the spreadsheet that I want to add some
DDE functionality to. I can trap the event just fine with a
Worksheet_Change() and do all the Excel-side stuff ok, but when I call the
subroutine with the DDEInitiate() call in it, the C app never gets the
WM_DDE_INITIATE message. Here's the bizarre part - in the VB editor in
debug mode, I can trigger that subroutine and step through it, and
DDEInitiate sends the message to my C app, but when that subroutine is
called as a result of my trapped event, the message doesn't get through.
Any ideas??
Thanks!
-- Jeff Brush