>>
>>Is anyone familiar with the consequences of an EXE that's built with VFP7 (SP1) and run with VFP6R.DLL (using the -d parameter)?
>>
>>
>What would this be good for? VFP6 and VFP7-applications can peacefully live together each
>using its runtimes. Is it for distribution-purposes?
I can easily automate the update of application files (with Installshield), but I know of no method to automate the update of desktop-icons and items in the startmenu. As you probably know, it's possible to specify the runtime library with the startup parameter -d, and this is actually happening on the many install bases. I'm investigating what the risks are when people ignore written instructions on this topic. Currently, the application does not use any vfp7 specific features. The exe is the only part that's compiled in vfp7, because it was the solution to some hard to tackle c05 errors.
Some official or unofficial comment on this topic may provide useful insights.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
