This utility depends on certain syntax of the PowerBuilder datawindow
and information from the PowerBuilder catalog tables.  Therefore it
has a number of limitations:

1.  You need to connect to the database that the datawindow references
    for the utility to operate correctly (this almost goes without
    saying, but I said it anyway).

2.  The SQL for the datawindow must be stored in graphic format.  That
    only requires the utility to parse out one particular SQL syntax.
    There are too many variations in the syntax for each database for
    the utility to handle datawindows where the SQL is stored as text.

3.  Currently, the utility only looks up the columns in the table that
    the datawindow is set to update.  Therefore:
	(a) the datawindow must have an update specification and
	(b) it will not display columns from other referenced tables
    It is possible to parse the datawindow syntax to read all of the
    tables referenced by the datawindow and show all of those columns.
    However, since I was primarily concerned with the columns that the
    datawindow would eventually update, I did not provide this
    capability.

4.  The table owner that the PB catalog tables are created under (not
    to mention datatypes, etc.) vary from one database vendor to
    another.  Therefore, the datawindow used to display the table
    column information has to be specific to the target database
    vendor.  I've included datawindows for Oracle, Sybase and Watcom
    (SQL Anywhere), the databases I do about 90% of my work against.
    You'll have to create that datawindow for other databases.  I
    recommend you use one of the existing datawindows as a 'template' 
    and store it under a different name after modifying it's syntax to
    work against your particular database vendor.  The open event of 
    w_main is where the datawindow object is dynamically assigned to the
    datawindow control based on the database vendor in use.

5.  When you create a new column in the datawindow, it is added to
    table definition within the datawindow and placed on the
    surface of the datawindow.  It is not added to the update
    specifications, given a tab order, edit style, etc.  I recommend
    using the 'sister' of this utility (DWCOLNFO) to set those
    attributes after saving the new datawindow definition using
    this utility.


	    