Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Setup unable to start DDE conversation wth the desktop
Message
From
03/08/2000 15:59:40
 
 
To
03/08/2000 15:48:51
Bill Drew
Independent Consultant
Chicago, Illinois, United States
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00399642
Message ID:
00400686
Views:
16
>>>What the heck is a DDE conversation and why would setup want to have one with a desktop?
>>>
>>
>>This sounds like something that uses an older installer, that made calls to the Program manager to create shortcuts rather than calling the IShellLink API either directly or via COM. What are you using for an installer?
>>
>>>Sometimes I get this error when testing setup and some of the people who install the program from my CDs also report this error. I click "Ignore" and everything seems to go along fine. The program runs. But it is annoying and to new users unsettling.
>>>
>>>I often find myself conversing with the wall but only when I'm really tired with the desktop.
>
>This occurs with VFP setup. But not always. The setup seems standard: nine files, one of which is a large CAB file. There is one active x control. 2 Icons but they don't end up on the desktop.

I'd make sure that you have the current Setup Wizard components for whichever version of VFP you're using by checking msdn.microsoft.com/vfoxpro and grabbing any updates that have not been applied or superceded. It has nothing to do with the location of shortcuts on the Desktop; the original 16 bit Setup used a DDE conversation with ProgMan to create shortcuts, which Setup Wizard does do for each file flagged as a PM item in Setup Wizard.
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Previous
Reply
Map
View

Click here to load this message in the networking platform