There was a problem sending the command to the program.

[Steve]

I am getting this 'useful' warning dialog box,

SOMETIMES, when I run an Access mdb Database,

which calls WshShell to open an ade database.

This seems to happen much more frequently although not each time in
XP, although I have seen it in 2000.

Does anyone know how to actually work out what the 'problem' is and
what 'command' is being sent to what 'program'.

The fact that we are getting this problem not consistently, is pretty
annoying to say the least.

If this warning dialog was made to contain little hints like the above
it may help to track down the problem, and work around it or
something.

HELP!!!!!!

 

[Will Denny]

Hi

You may like to direct your question to an Access News Group:

news://msnews.microsoft.com/microsoft.public.access

--

Will Denny
MS-MVP Windows - Shell/User


| I am getting this 'useful' warning dialog box,
|
| SOMETIMES, when I run an Access mdb Database,
|
| which calls WshShell to open an ade database.
|
| This seems to happen much more frequently although not each time in
| XP, although I have seen it in 2000.
|
| Does anyone know how to actually work out what the 'problem' is and
| what 'command' is being sent to what 'program'.
|
| The fact that we are getting this problem not consistently, is pretty
| annoying to say the least.
|
| If this warning dialog was made to contain little hints like the above
| it may help to track down the problem, and work around it or
| something.
|
| HELP!!!!!!

 

[frodo]

do you have zone alarm installed?

"a problem occured sending the command..." is a DDE problem, when a
program sends a request to another via the DDE channel (dynamic data
exchange).

ZA can sometimes stop this sort of peer-to-peer communication inside a
box. to verify, shutdown ZA and see if the symptom goes away. If so it's
ZA.

[Try this: open a folder window, right-click upper left corner folder
icon, choose "search". Do you get the error message? shutdown ZA, try
again, it works. in this case ZA is blocking the DDE msg to
explorer.exe].

To solve, add these two ip addresses to the Trusted Zone: 0.0.0.0 and
127.0.0.1. Then make sure the receiving program has "allow" checked in
its "trusted zone access" column.

 

[Monte Tucker]

I've had this problem for at least six months. I added 0.0.0.0 back into ZA
as a trusted site, and it works. Thanks a lot!

I guess I was too secure.