The message below is coming from FoxWeb, which means that you are getting closer: FoxWeb is functional and configured to run with IIS.
The reason you are unable to call your copy of NameSearch.fwx is because you copied it to a location that is outside the FoxWeb program root. All FoxWeb scripts MUST reside within the FoxWeb Program Root and its sub-folders. By default, the FoxWeb Program Root is c:\Program Files\FoxWeb\Programs.
If you want to work on a copy of NameSearch.fwx, copy all the files from c:\Program Files\FoxWeb\Programs\NameSearch to c:\Program Files\FoxWeb\Programs\Playground. You should then be able to call the script with the following URL:
Sent by George Gambill on 09/24/2007 07:18:31 AM:
Now, (on my computer running the eval FoxWeb software) when I enter http://127.0.0.1/namesearch.fwx in MS IE I get the following message:
NAMESEARCH.FWX and it's supporting tables (names.dbf and names.cdx) were coppied to C:\FoxWeb\Playground from from:
FoxWeb IS running and I believe it is configured well (Probably not).
It works on Lews computer running the registered FoxWeb.
It seems to me that IIS is doing well (which wasn't true before) as other web pages (HTML) display well.
Any ideas what in the setup might cause this?
Sent by FoxWeb Support on 09/21/2007 01:10:04 PM:
What URL are you using to call NameSearch? I have a feeling that you are reading the file directly from your browser, instead of calling it through IIS and FoxWeb. You can’t simply type regular Windows paths in your browser, because in this case the browser simply opens the file directly, without going through IIS and FoxWeb. This the reason why the code between the <% and %> tags is displayed in the browser window, instead of getting executed. URLs must start with http://, as described in the documentation.
I suggest that you take a step back and make sure that everything is set up and working properly:
Make sure the IIS is functional:
In order to make sure that IIS is functional, you must first be able to open a browser on the server and get a result with the URL http://localhost/.
Make sure that FoxWeb is started:
Follow the instructions in the Setup and First Steps page of the FoxWeb documentation. For now don’t configure FoxWeb to run as a service. Once you start it (either from the FoxWeb icon in the Start menu, or from the Start FoxWeb button in the FoxWeb Control Center), you should be able to see a FoxWeb icon in the notification (tray) area in the lower right part of your screen. If you double-click on that icon, you should see a status window, listing one, or more active channels. If you don’t see this, then FoxWeb is not started.
Make sure that FoxWeb and IIS are configured to work together:
Again, follow the instructions in the Setup and First Steps page to call fw_admin.fwx, as well as the sample scripts. Verify that you can call the samples that come with FoxWeb, before running any other scripts.
Sent by George Gambill on 09/21/2007 12:28:10 PM:
We have tried to setup FowWeb per the documentatoins.
When we try to run the NameSearch demo (as a learning curve thing) we get the following pace. It seems to not want to wait for our input in the name field and calims no results.
This example illustrates how simple it is to write FoxWeb applications. The code searches a FoxPro table for matches on the name entered by the user. Partial matches also yield results. For Example "mo" will find both "Monroe" and "Morrison." The search is not case sensitive. To see all the names in the database just leave the Name entry blank.Name: ">
Your Search Yielded No Results