Illegal FoxWeb Commands

The error handler built into FoxWeb will handle all errors that can be trapped by VFP's ON ERROR command. Your programs should be able to recover gracefully if they contain one of these errors. In these cases the error handler will add an entry to the FoxWeb Error Log. Even though the FoxWeb error handler will handle pretty much everything, there are still some ways to damage the FoxWeb environment. In these cases the channel will be re-started if the Restart Channels option is enabled. Following is a list of commands to avoid:

You should not use commands that will stop or alter program execution: QUIT, SUSPEND, WAIT, BROWSE, APPEND, EDIT, RETURN TO MASTER, etc.

Some data manipulation commands (REPLACE, DELETE, INSERT, etc.) will also stop program execution and bring up the Open File dialog if there is no table open in the current area.

You should also never include any of the following commands that release or replace existing memory variables, forms, or external function definitions: CLOSE ALL, CLEAR ALL, CLEAR MEMVAR, CLEAR MEMORY, CLEAR DLLS, CLEAR WINDOWS, RELEASE ALL, RELEASE LIKE *, RESTORE FROM.

Variable Names

FoxWeb's objects are all regular VFP objects, so they will be destroyed if scripts declare variables with the same name, most probably causing the channel to crash. Please avoid creating any variables with the same names as any of the FoxWeb objects, unless you declare them as local first. Obviously, if you create a local variable with the same name as one of FoxWeb's objects, you will not be able to access this object in your scripts.

© Aegis Group