>>>>You'll need to access the IShellLink API to create the shortcuts; George Tasker has created a wrapper .DLL that makes the IShellLink API accessible from within VFP; it can be downloaded from the files section here on UT. If you have the Windows Scripting Host installed on the target system, the Wscript.Shell OLE Automation object has a set of methods that make the IShellLink API available through the Automation object; it can create shortcuts not only for a local resource, but also for URLs (links to the InterNet).
>>>
>>>Thanks Ed. I got the wrapper .DLL, but still can't make it out. Can you show me how to code it, practically.
>>
>>Hi Nond,
>>
>>Have you checked the help file? It includes straightforward syntax examples in VFP. In my work, I include the dll in the setup disk, and, in the wizard indicate that it should be put in the windows system directory.
>
>Hi George,
>I read through the lnkfile.hlp and understand the examples. But this may be my weakness. I don't understand what should be put as the post-installation executable file to automatically create my shortcut and menu in the Program menu after the file copying process.

Hi Nond,

To put something on the desktop, you'd have to retrieve the desktop folder name (using the DLL), then create the shortcut, supplying the link file name (including the path of the desktop) and the target executable.

The categories under the Start Menu\Programs are simply folders (directories). You can create your own with the VFP MD command. Then simply create the link file in that directory. You should, however, use the DLL to retrieve the Start Menu\Programs directory.

hth,