----------------------------------------------------------Unsup.prg Utility ----------------------------------------------------------Microsoft makes no warranty, implied or otherwise, regarding this codes' performance or reliability.

-----------------------Purpose of Utility -----------------------The utility or program was written in Visual FoxPro's Xbase language and Visual FoxPro is required to execute the code. Utility searches a .TXT or .PRG file for commands that are co nsidered unsupported when using the VFP ODBC driver. -----------------------How to Use This Document -----------------------To view the ReadMe file in Windows Notepad, maximize the Notepad window and clic k Word Wrap on the Edit menu. To print the ReadMe file, open it in Notepad or another word proc essor, and then use the Print command on the File menu. -------CONTENTS -------1. 2. 3. 4. Installation Trigger Code: Input Data Log File: Output Data Executing the Unsup.prg program.

Installation --------Follow the instructions below to install the files: 1. Create a directory called c:\unsup. 2. Download the unsup.exe self extracting file into the c:\unsup directory. 3. Execute unsup.exe. The following files should now appear in the c:\unsup directory: Files Included Purpose unsup.prg Utility/Visual FoxPro Code that finds un supported commands. unsup.dbf Database file of unsupported commands; i t is used by the unsup.prg. tastrade.txt Copy of Tastrade stored procedures that can be used to demonstrate utility. Readme.txt This readme file. Trigger Code: Input Data --------The unsup.prg takes an ASCII text file as input. Both .TXT and .PRG files could be used as input. It is necessary to copy the Stored Procedure code from the Visual FoxPro database to a

.TXT or .PRG file before running the unsup.prg. Log File: Output Data ---------The output log file is called prob.log by default, and for every line of code th at the unsup.prg utility suspects having an unsupported command in it, it writes the following informatio n to the log file: <<The actual line of code that it things may cause a problem.>> <<Line number that it found the problem>><<The unsupported command that it thing s it found in that line.>> Note: The unsup.prg program may be overly sensitive in flagging certain lines of code as containing unsupported code. For example, a line of code could contain "!" used as a not o perator which is supported, but the line would be flagged anyway because the "!" could also be used as a run command; thus the utility will flag the line anyway. Executing the unsup.prg program ---------Visual FoxPro is required to execute the unsup.prg, the program that finds unsup ported commands. To execute the utility: 1. Set default to c:\unsup or the directory where unsup.prg, unsup.dbf, and tas trade.dbc have been placed. 2. From the command window, type in the following and press return: DO unsup.prg 3. A dialog box will be displayed that lets the user choice the file that conta ins the trigger code. Select the file that contains the trigger code and click on the Process button. 4. As the unsup.prg finds unsupported commands in the code, it will echo proble ms to the Visual FoxPro desktop and to the prob.log text log file. 5. After all the code has been processed, the prob.log file will be displayed f or viewing or printing.