Link to home
Start Free TrialLog in
Avatar of breauxlg
breauxlg

asked on

Turn off dde for access 2003 in server 2008

I'm getting the "There was a problem sending the command to the program" error when running an access 2003 database from the desktop on a server 2008 terminal server. I have checked and unchecked all the combinations on the advanced tab of the database and cannot get the message to go away. Where do I get rid of the dde process in this environment. On server 2008 the folder options, file association tab doesn't look like the older versions where you have a dde option. I guess it's somewhere in the registry, but I can't for the life of me find out where to go.
Avatar of breauxlg
breauxlg

ASKER

Thanks.
Avatar of Scott McDaniel (EE MVE )
Do you get this error while you're performing any specific task - for example, does it occur when you Open a Form, or when you enter data in a control, etc etc?

Have you performed maintenence on the database (i.e. Compact, Compile, Decompile, etc)?

The database basically just opens, runs a procedure, and closes. The prodecure runs and performs the intended function, but the message still appears. After clicking OK, it goes away, but it confuses the users to have that message pop up evertime the database runs. Thanks for caring enough to respond, by the way.
I have tried decompiling and recompiling, compacting and repairing, etc. to no avail.
What's the procedure? What does it do?
It just copies a front-end database to the desktop of the user.
Can you post the code that causes the error?
Here's the little database that generates the error. It does not generate the error on Server 2003.  BackupLoadWorks.zip
try going to this registry key:  HKEY_CLASSES_ROOT\Access.MDBFile\shell\Open\ddeexec

change the key name "ddeexec" to "NOddeexec".

I had a very similar problem and it fixed my issue.  My co-worker helped me with this issue.  We found that the ability to turn off DDE in Access was removed in current versions of windows, so you need to go into the registry to do it.  changing "ddeexec" to "NOddexec" is kink of a hack, but it worked.

good luck.
jbodager - There is no key in the registry at that point. I don't have Access.MDBFile under HKEY_CLASSES_ROOT. That looked hopeful, though.
ASKER CERTIFIED SOLUTION
Avatar of jbodager
jbodager

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I found the access.application registry entry and renamed the ddeexec to noddeexec and the message went away. Thanks jbodager.
I'm just glad someone was still looking at my problem. Thanks.