%META:TOPICPARENT{name="ConfigureProgressTableview"}%

= Setting Up Tableview Functionality for SQL-89 Connections on Windows =

The following instructions will enable you to run **{{{setup.p}}}** on a Windows host.

//**Please note** -- you must have a 4GL Development System license to run this script. Client Networking alone is not sufficient. This script does not need to be run on the client host which will use the resulting tableview files, however -- the script may be run on any host which has the licensed 4GL Development System, and the same versions of the Client Networking libraries as will be used on the ODBC client host(s).//

# Confirm environment variable settings --
#* {{{DLC}}} variable must be set to the main Progress directory, e.g., {{{C:\Program Files\Progress}}})
#* {{{PATH}}} variable must include the expanded {{{$DLC\bin}}} directory, e.g., {{{C:\Program Files\Progress\bin}}}
# Search your OpenLink installation for a file called {{{setup.p}}}. Make note of the directory in which it is found. (By default, we will install this in one of the following --
#* Single-Tier
#** {{{C:\Program Files\OpenLink\lite32\}}} 
#** {{{C:\Program Files\OpenLink Software\UDA\lite32\}}} 
#* Multi-Tier
#** {{{C:\Program Files\OpenLink\Scripts\Progress\}}} 
#** {{{C:\Program Files\OpenLink Software\UDA\Scripts\Progress\}}}
# Start a CMD/DOS session (**Start** menu >> **Run...** >> **{{{CMD}}}**), and navigate to the directory you found above; for instance --
{{{
cd C:\Program Files\OpenLink\lite32
}}}
# Execute the following command to start the script --
{{{
pro -p setup.p
}}}
# The script will present a screen of instructions. Type any key to get the entry dialog. 
# Enter your target database name, and the connection parameters if running in sockets mode. When entering paths, if there are any spaces, e.g., {{{C:\Program Files\}}}, you must enclose the entire path in quotation marks
{{{
1  </full/path/to/database/file.db>
   -S <port number or service name> -H <host> -N tcp -ld <logical name> -trig <path to triggers file directory>
}}}
For instance --
{{{
1  C:\Progress\DBS\demo.db
   -S prosports -H localhost -N tcp -ld psports -trig C:\Progress\DBS\triggers
}}}
-- or --
{{{
1  "C:\Program Files\Progress\DBS\demo.db"
   -S 6100 -H progress-host.example.com -N tcp -ld psports -trig "C:\Program Files\Progress\DBS\triggers"
}}}
# Hit the **enter** key when complete. The script will pause briefly to test the connection. 
# If you have another target database, enter that information. When you have no more targets, hit the **F4** key.
# You will now be prompted for the location to store the new files, and the name to use for those files. Note that setup.p cannot create new directories, so you must choose a location that already exists. For most predictable results, enter the same location as you started with (where setup.p is), and the default filename, `tableview` -- 
{{{
"C:\Program Files\OpenLink\lite32"
tableview
}}}
# Hit the **enter** key when ready. The script will save the files, and present a NOTICE about what it has done. //**Please note** -- the NOTICE was written for Multi-Tier users, and may not be exactly applicable to you, if using Single-Tier.//
# You can now close the CMD/DOS window. 
# Now, go to the Data Sources (ODBC) control panel, locate and select your DSN, and click CONFIGURE.
# On the second pane of the setup dialog, the **Session options** field should generally be left blank; the **Database options** should now contain only the **{{{-pf <full path and file name to .pf file>}}}**, and the **Table view** field should contain **{{{<full path and file name to .dat file>}}}**.
#* **{{{Session options}}}** &mdash; (blank)
#* **{{{Database options}}}** &mdash; {{{-pf "C:\Program Files\OpenLink\lite32\tableview.pf"}}} 
#* **{{{Table view}}}** &mdash; {{{"C:\Program Files\OpenLink\lite32\tableview.dat"}}} </blockquote>