>I have not tried to upgrade any of my VMP 3 projects to VMP4, and do not have my manual with me at this time. Be sure to post your questions of the VMP forum.
>
>You should have one directory for \xlib, etc., for your VMP 3 version. When you install VMP 4, you create a new directory \vmp4, etc. By referencing Vmp4\xlib in your config.xxd file, and attempting to rebuild the project, you should quickly find out what is happening. Either you will get a clean build or error messages.
>
>It seems strange reading the messages you are obtaining. Pathing problems have given me the biggest problem with this product. Once I understood what was required, I got over that hump. By the way, the security model in this version is very nice. Above all, remain cool.
>
>When you resolve this issue, you will be able to write your own instructions on how to upgrade from VMP 3 to VMP 4. And I know your instructions will work. You can tell that tech writers were not involved with this manual. We developers take many things for granted from our audience, and do not always include steps necessary for someone else to successfully follow our instructions.
>
>Tom

I did not find any VMP forum on the Universal Thread as you mentioned in your note. But I do agree that VMP documentation is badly written for training new developers. Once I understand the process by a lot of trial-and-error the manuals are exactly accurate but by then it is too late; I already have spent the time trying to figure them out.