I have no explation either. I like ActiveVFP and appreciate your support of the product. Have used it in the past and will continue to use it in the future.

Thanks
Gaylen

>The only thing I can think of is if there is some sort of automatic pathing in your config file maybe or maybe this is sort of a flukey thing in XP. This never happens to me in Win2K. Anyway, you know how to run WebAppBuilder.app in your environment now - directly from VFP instead of the AVFP file group...
>>Only 1 WebbAppbuilder.app and it is in \dotcomsolution. When called from the vfp window it works, when called from the start menu, it errors. I added some text to the form so I knew I was using the same appliction both times.
>>
>>Gaylen
>>
>>
>>>This is interesting. The original WebAppBuilder is in the \dotcomsolution directory, but, unless you directed your compile there, you probably ran the one in the same directory as the project. So, it looks like the one you compiled is working. Could you verify this? You probably have 1 WebAppBuilder in \dotcomsolution and 1 in \dotcomsolution\avfpdemo2 ...
>>>>Don't know if this will help. I substituted the code below and recompiled the program to c:\dotComSolutions directory. When I ran the webappbuilder.app program from within the command window the program does just fine and will build the correct mtdll. When I run that same app from the start menu I get the error message "feature not Available" and the mtdll is not created. The start menu calls the same WebAppBuilder application as I used in the command window. Not sure what to make of all of this.
>>>>
>>>>I am running VFP7 SP1.
>>>>
>>>>Gaylen