7/27/2019 READMEkfkfkfk

1/2

-----------------------------------------------------------Unsup.prg Utility-----------------------------------------------------------

Microsoft makes no warranty, implied or otherwise, regarding thiscodes' performance or reliability.------------------------Purpose of Utility------------------------

The utility or program was written in Visual FoxPro's Xbase language and VisualFoxPro is required toexecute the code. Utility searches a .TXT or .PRG file for commands that are considered unsupportedwhen using the VFP ODBC driver.

------------------------How to Use This Document------------------------

To view the ReadMe file in Windows Notepad, maximize the Notepad window and click Word Wrap onthe Edit menu. To print the ReadMe file, open it in Notepad or another word proc

essor, and then use thePrint command on the File menu.

--------CONTENTS--------

1. Installation2. Trigger Code: Input Data3. Log File: Output Data4. 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 Purposeunsup.prg Utility/Visual FoxPro Code that finds unsupported commands.unsup.dbf Database file of unsupported commands; it is used by the

unsup.prg.

tastrade.txt Copy of Tastrade stored procedures thatcan 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 couldbe used as input. It isnecessary to copy the Stored Procedure code from the Visual FoxPro database to a

7/27/2019 READMEkfkfkfk

2/2

.TXT or .PRG filebefore running the unsup.prg.

Log File: Output Data----------

The output log file is called prob.log by default, and for every line of code that the unsup.prg utilitysuspects having an unsupported command in it, it writes the following information to the log file:

Note: The unsup.prg program may be overly sensitive in flagging certain linesof code as containingunsupported code. For example, a line of code could contain "!" used as a not operator which is supported,but the line would be flagged anyway because the "!" could also be used as a runcommand; thus the utilitywill flag the line anyway.

Executing the unsup.prg program----------

Visual FoxPro is required to execute the unsup.prg, the program that finds unsupported commands. Toexecute the utility:1. Set default to c:\unsup or the directory where unsup.prg, unsup.dbf, and tastrade.dbc have been placed.2. From the command window, type in the following and press return:DO unsup.prg3. A dialog box will be displayed that lets the user choice the file that contains the trigger code. Selectthe 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 problems to the Visual FoxProdesktop and to the prob.log text log file.5. After all the code has been processed, the prob.log file will be displayed for viewing or printing.