>>Bob,
>>
>> what problems are you having? What operating system? How are you installing? (From the 5.0b CD, or from 5.0, and then upgrading.) There aren't many bugs in the basic product at this point -- it's something I've been using daily for the past 6 months (and for a year on the beta before that). I've always found installation to be straight-forward. There was a problem in the release product under NT, the fix to which was to create your own shortcut:
>>
>>c:\vfp5\vfp.exe c:\vpm5\vpm.app -t -cc:\vpm5\sappcfnw.fpw
>>
>>Note that there is a VFP bug: you can't installed VFP5 in a directory with a space in the name -- which is of course what will happen if you install the default DevStudio setup. Also, VPM does rely on paths (I have made my feelings clear on this ), so it's really best to install both VFP and VPM in folders off root directories.
>>
>>As a VFP thingie: you will mess up finding icon files in your setup disks if you install on other than the C: drive. This is an oldie but goldie which goes back to 3.0, doesn't strike everytime, but to my knowledge is still the case. VPM can be on any drive, although out of superstition I keep it, and the projects, all in folders off the C:\ root.
>>
>>Hank
>
>Basically, to get rid of this bug, you don't need to install VFP on C: drive. You need only to have all files for your projects on the C:.
>
>Vlad
That's interesting. I wonder if there's a KB on this?

Hank