Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Data on the WEB - best way to organize
Message
General information
Forum:
Visual FoxPro
Category:
Internet applications
Miscellaneous
Thread ID:
00749322
Message ID:
00750848
Views:
22
Nadya,
The webAppBuilder is trying to compile the new project. Since you have VFP6SP5, it does not recognize STREXTRACT and EXECSCRIPT. So I would recommend commenting out any code that mentions those commands in the ActiveVFP.prg and Main.prg(I probably should be using a preprocessor directive to conditionaly include those commands). They are purely optional commands. I think it didn't work because it didn't compile properly. The tlbimp should work once it compiles properly.
BTW, please start posting these questions in the ActiveVFP section...
>Claude,
>
>Setup seems to run fine.
>
>>First off, did the setup run without any errors? It should have popped up the demo app at the end of setup.
>>The Documentation link should be correct in the AVFP Folder it creates on the desktop and under Start/Programs.
>
>>It should be the readonly directory under whatever directory you installed to. In your case this should be:c:\activevfp\dotcomsolutions\AVFPdemo2r .
>
>Found documentation and printed, thanks.
>
>>What are the errors you got using WebAppBuilder?
>
>1. Unable to find unknown STREXTRACT
>2. Unable to find unknown EXECSCRIPT (note, I'm still using VFP6 - too bad for me, I understand).
>
>Then it searches for tlbImp.exe (It's in Miscrosoft Visual Studio .NET directory, not the one it tries to search). After I pointed to it, it gives 500.100 error:
>=======================================================
>The page cannot be displayed
>There is a problem with the page you are trying to reach and it cannot be displayed.
>
>--------------------------------------------------------------------------------
>
>Please try the following:
>
>Click the Refresh button, or try again later.
>
>Open the localhost home page, and then look for links to the information you want.
>HTTP 500.100 - Internal Server Error - ASP error
>Internet Information Services
>
>--------------------------------------------------------------------------------
>
>Technical Information (for support personnel)
>
>Error Type:
>onstartpage err#= 1238 line= 1 No PARAMETER statement is found.1238 No PARAMETER statement is found. .NULL. .NULL. .NULL. .NULL. .NULL. c:\webdevelopment_credit\creditrecords\creditrecords.dll (0x80020009)
>c:\webdevelopment_credit\creditrecords\creditrecords.dll
>/CreditRecords/default.asp, line 4
>
>
>Browser Type:
>Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705)
>
>Page:
>GET /CreditRecords/default.asp
>
>Time:
>Friday, February 07, 2003, 9:12:09 AM
>
>
>More information:
>Microsoft Support
>
>===================================
>Also, what OS?
>
>Windows 2000.
>
>When I tried to build app again, it gave me 404 errors.
>
>Also this is I found in CreditRecords.err file:
>-----------------------------------------------------
>Compiling c:\webdevelopment_credit\creditrecords\prg\combase.prg
>Procedure Destroy() as Void
>Error in line 43: Command contains unrecognized phrase/keyword.
>Procedure GetDebugObject() as Object
>Error in line 58: Command contains unrecognized phrase/keyword.
>
>Compiling c:\webdevelopment_credit\creditrecords\prg\activevfp.prg
>Procedure Init() as Boolean
>Error in line 38: Command contains unrecognized phrase/keyword.
>Procedure OnStartPage(toContext as Object) as Void
>Error in line 71: Command contains unrecognized phrase/keyword.
>Procedure OnStartPage(toContext as Object) as Void
>Error in line 71: Function name is missing ).
>
>Program c:\webdevelopment_credit\creditrecords\prg\main.prg has the following errors:
> Unknown STREXTRACT - Undefined
>
>Program c:\webdevelopment_credit\creditrecords\prg\activevfp.prg has the following errors:
> Unknown STREXTRACT - Undefined
> Unknown EXECSCRIPT - Undefined
>------------------------------------------------------------
>So, it could not work in VFP6, as it claims. It should work in VFP7 and VFP8. I'm not sure, when we'll start to use VFP8 here. We never switched to VFP7...
Previous
Reply
Map
View

Click here to load this message in the networking platform