To elaborate a little more, here is what I did. I opened VFP in directory c:\program files\dotcomsolution. Then opened the project which was in c:\program files\dotcomsolution\avfpdemo2. I opened the webappbuilder form in the project and used the project run command to run the form. It failed at the aforementioned place. I then put the wabcmd.prg in the c:\program files\DotComSolution folder and it ran without the error and this time the mtdll were created. I tried to recompile the project but it displayed the error without the wabcmd.prg file. Interestingly enough the WABcmd.prg is part of the project, but evidently it doesn't recognize it .

Hope this helps.

Gaylen



>OK! So the problem is probably that it can't find WABcmd. So, you're saying that when wabcmd.prg is in the same directory as the project. WebAppBuilder is working correctly?? Thanks!
>>Claude
>>
>>I ran the WebAppBuilder from the Project using 'run' command. The error message 'feature not available' is triggered by the following line of code. Said it couldn't find Wabcmd.prg.
>>
>>

>>		DO WABcmd WITH lcCMD
>>

>>
>>I moved the WABcmd.prg file to c:\program files\avfpdemo2 directory and the error message dissappeared and the mtdll was created for that application. In previous attempts the mtdll was not created when I used WebAppBuilder. It didn't create the virtual direcories but when I manually created them I was able to get to the new applications default screen.
>>
>>Gaylen
>>
>>>h_point.cur is in your \vfp7\Ffc\Graphics folder. WebAppBuilder is compiled into an app, not a .dll. The main logic is in the WebAPpBuilder form. If you go into that form and click on the 'Build Web App now!' button, you'll see the main logic.
>>>We need to find out what 'feature' is not available. Any help in this regard would be appreciated. Apparently, this is either an XP thing or something particular to your environment...
>>>>Claude -
>>>>When I try to recompile the webappbuilder - error message h_point.cur not found. In the past a dll was created with the same name as the application and contains the 'main.prg'. That file is not created using WebAppBuilder.
>>>>
>>>>The error message I was getting was 'feature not available'.
>>>>
>>>>Gaylen
>>>>
>>>>
>>>>>Sounds like the WebAppBuilder app is not finishing and PostSetup is never being run because it doesn't get that far. Could you recompile WebAppBuilder and try again and please let me know if it works? I didn't know you were getting error messages. Your version of WebAppBuilder has been pre-compiled in VFP 7 SP1 by me, but, it sure sounds like it doesn't like that file based on your error messages.
>>>>>The naming convention problem has been fixed.
>>>>>The syntax for calling the Virtual Directory code is:
>>>>>setIISAdmin(lcName,lcFolder,lcDomain,lcWebSite) which correspond to the parameters for WebAppBuilder, but, like I said, that probably isn't the problem.
>>>>>>I called the app 'test' and the directory 'mytestdir' as I knew about the naming convention problem. When I first run the web app builder it say the resource file is not valid - Do you to create new one. I answer yes. Next an error message come that says 'feature not available'. I respond with ignore. Then a prompt comes up about asp.net - I respond with 'NO'. It then complete its work and the log created says test web application build was completed sucessfully.
>>>>>>
>>>>>>I didn't see any browser messages about whether the postup ran or not.
>>>>>>
>>>>>>I would be glad to run code below, however help me with the syntex for calling the functions and the parameters.
>>>>>>
>>>>>>Gaylen
>>>>>>