DEVELOPER TOOL KIT

fileProGI
INSTRUCTION
MANUAL

Written by: Christopher L. Henschen

Copyrighted by: Henschen and Associates, Inc

(All rights reserved 2002)
 INTRODUCTION

This manual is written to assist the developers in setting up and using the Developer Tool Kit
written by the Visual Legacy Group, Inc,. also known as WinFAST in conjunction with and
distributed by fP Technologies, Inc. Mr. Christopher L. Henschen, the author of this manual,
heads the development team of Henschen and Associates, Inc,. and was the liaison and
coordinator in the development of fileProGI and the Developer Tool Kit.

Developer Tool Kit:

Section 1: Setting Up a Client Executable ..........................................................Page 1

Section 2: Application Configuration Table - Developer ...................................Page 2

System Settings ..................................................................................Page 2

Menu Screen Details ..........................................................................Page 3

Data Entry Screen Detail ....................................................................Page 4

Drop Down Lists ................................................................................Page 6

Exercise 2 - Local Dropdowns ...........................................................Page 8

fileProGI Enhancements:
Section 1: Status Bar & Special Features ............................................................Page 9

Section 2: fileProGI – Show and Edit Buttons....................................................Page 14

Section 3: New Message Send Commands .........................................................Page 17

Section 4: Built-in Viewing (Photos, text, etc.) ..................................................Page 17

Section 5: Embedded Files/Graphics ..................................................................Page 18

Section 6: Launching Client Side Applications ..................................................Page 20

Section 7: Additional Message Send Options .....................................................Page 24

Section 8: Miscellaneous Changes ......................................................................Page 26

Section 9: Tips and Tricks ..................................................................................Page 28

Section 10: Slide Presentation...............................................................................Page 30

i
 SETTING UP A CLIENT EXECUTABLE

After modifying all the parameters within your development system, the next step is to configure
a client.

1) Change directories to the fpGIdev folder. (These systems have it under c:\appl\fp\fpgidev.
The default location would normally be c:\fp\fpgidev.)

2) Run fpGIdev by double clicking on the appropriate icon.

3) Click on the “Setup Configuration” button (see

right).

4) Click on the “Save Configuration Button” (see

right). A statement may appear stating “the
deployable configuration file....\fpgiConfig.dat
already exists.” If so, answer “yes” to override
it.

5) Once this has been saved, exit from the fpGIdev

file.

6) Create a directory called fileproGI, or fpgi.

(This can be done by right clicking in the “Setup Configuration” button
fpGIdev folder and selecting New
Folder,
and then typing in the new name.)

7) Copy fpgiConfig.dat from within the ConfigFile

directory over to your new directory.

8) Take the GI runtime files, fileproGI.exe and

fplic.dat, which you received from Filepro and
copy to this directory.

9) Copy your dd0.txt file to this directory.

You are now ready to run your new runtime version.

This directory could be zipped and turned into an
executable installation using a program such as
winzip. You would then be able to extract files to
other computers at the site “Save Configuration” button

1
 APPLICATION CONFIGURATION TABLE - DEVELOPER

The Developer is the module which opens the door to features similar to those you would find
using Windows. When the Developer is loaded there is a GIserver directory within fp.
Eventually, we will discuss this in further detail but for now, let’s just say the executable is
named fpGIdev. When opening fpGIdev, you will notice that the opening screen has a couple of
options the runtime version doesn’t. Clicking the “Setup Configuration” button will bring up
the “Identify Server” window. Click on the “Application Configuration Table” button. Once
you do, you will see tabs along the top of the screen: System Settings, Menu Screen Details, Data
Entry Screen Details, and Drop Down Lists.

“Setup Configuration” button

“Application Configuration Table” button

SYSTEM SETTINGS

To the right, you will see the “System

Settings” screen. By checking “Logging
Enabled” a file will be created within the
local directory of the executable of the
GIclients. This file, fileproGI.*.*.*.*.dat,
will only grow to a maximum, so there is
no is no need to worry about filling your
drive space. It is recommended not to
adjust any of the items on this page except
for those located within the “filePro Flags”
section. In the “filePro Flags“section, you
will see a list of check boxes.
2
Suppress Status Buttons - This will suppress edit descriptions defined with the new \{} style
buttons (see edit buttons on page 15). If the edit doesn’t contain the button format within the
edit description, the text will show on the last line of the screen. This is helpful if you prefer to
use drop downs but do not desire to have the edit show in GI; however, in the character version
the edits will remain.

Use Bevels for Protected Edit Fields - This enables a three-dimensional look to protected fields
on the filePro screens.

Sound the Bell - Enable/disables the error bell sound.

Use filePro colors in a Browse - Enables/disables the use of filePro colors in a browse window.

Show Cursor in DE Screen - Enable/disable the blinking block cursor on the screen usually
associated with character screen types.

Show ‘Appearance’ Button in DE Screens - This allows you to enable the “Appearance” option
on the toolbar of the data entry screens, and the “Option” option on the toolbar of the menu
screens. Enabling will give the user the ability to change the colors and characteristics of the
screens.

MENU SCREEN DETAILS

To the right, you will see the “Menu

Screen Details” screen. The Default
Folder for Custom HTML Menus is
located here. If a path is placed here,
any calls to html menus are relative to
this location. Developers who want to
use absolute paths should leave this
blank, otherwise, the call to the
absolute path will be appended to the
default folder.

You should uncheck the “Pass Keystrokes thru HTML” box if you don’t want the keys passed
through. This is used in custom html menus.

Action keys are the labels for menu items, which appear to the left in character versions. You
should check the “Show Action Keys in Menu” if you would like for this to happen.

3
The “Define Popup Menu” button consists of a table of commands, which show up when you
right-click on menus.

To add features:
1) Under the “Enabled’ column, change the statement from “false” to “true.”
2) Under the “Menu Item” column, type in the label you want to appear in the right-clicked
menu. Example: “Help”
3) Under the “Send to Server” column, place the keyboard option you wish to send upon
selecting the item. Example: Click “Help” would be the same as depressing <F10> key.
4) To preview, right-click on the Test Popup Here edit box.
5) Finally, click the
“Done–Save
Changes” button.

DATA ENTRY SCREEN

DETAILS

At the right, you will see the “Data

Entry Screen Details” screen. As
you can see, the developer is able
to place their company’s name or
other information in the “Title Bar”
field. It is recommended to leave
the color selection based on the
terminal color, instead of based on
attributes. However, feel free to
change the colors under the “Setup
Colors and Fonts” button.

4
 Colors are associated with the
color on the
character screen.
For example, to set
the colors of this
blue/white screen
with red/white
reverse, follow the background color for blue down to
the foreground color for white in the “Customize Form
Colors” table.
Click the box
where the two
colors meet.

From here one can adjust the foreground and background

colors using the paint palette. Even though there is a “Set
Edit Font” option, it is highly recommended not to use this
option. The fonts in use have been selected to allow for the best viewing. Changing them may
cause loss of the cursor in edit fields and undesirable spacing between letters. After making the
color changes, click the “OK” button. The changes will become the new color(s) for the GI
program, associated with the character colors.

Other options include setting the Edit Normal, Edit Hilite, and Default colors, with edits being
the field location where the data is entered. By clicking the buttons you are allowed to set the
form’s background and text color. All button colors used within the application can be changed
in the same manner. The “Gradient Color” button allows for changing of colors boarding the
typical filePro screen boarders and the login splash screen.

If we return to the “GUI Data Entry Screen Characteristics” screen, you will see that the check
boxes for automatic links to WWW addresses and email are set to “off.” By checking these
boxes, text formats such as [email protected] and www.fptech.com become executable by
double-clicking the mouse on the titles. The “Popup for Edit Fields” button is the same as
the”Define Popup Menu” button mentioned above, except that it works only in the edit fields.
The “folders containing image/text files for display” have the same conditions mentioned above
for html menu paths; however, if absolute paths are desired do not place anything in these
locations.

5
 DROPDOWN LISTS

Dropdowns can be added to give you a Windows

look and feel. It order to create these dropdowns you must have the developer component.
Dropdowns consist of text files defined by the programmer. In order for
these dropdowns to appear, a consistent set of field labels on the screen
must be adhered too. Once the programmer knows the label context used
to trigger the dropdown, they will highlight an empty line, or the item to
be changed, from the browse list at the bottom of the screen. At this
point, the user can define the dropdown using the information at the top of
the screen.

To the right, you will see the “Drop Down Lists” screen. You will need to fill in the following
fields in order to create a dropdown.

Enabled - By selecting “true” it will

allow the programmer to have an
active dropdown defined. If set to
“False” it will make the dropdown
inactive.

Description of this Dropdown – A

user defined description or comment
used to describe the dropdown.

Label for the Data Entry Field – This

is the field label used to determine
whether or not a dropdown should be
placed on the screen. This includes both inputs and input popups.

6
File containing the Dropdown entries – This is the text file that contains the dropdown text.
Clicking on the file folder image to the right of this field allows you to navigate to the desired
text file and edit it from this location.

Number of Lines to Ignore at Top of File – Usually this would be “0"; however, if you need an
offset from the top of the field which will NOT display headings, it is provided.

Title to be shown at the top of the Dropdown – This is where you would enter the title(s) of the
columns that will be shown in the dropdowns.

Delimiter separating fields for multicolumn dropdown – This is a user definable delimiter for
cases when the semicolon might be used as part of the dropdown descriptions.
Example: Code;Description NOTE: no spaces

Search Row & Col – Zero being the default allows for the checking of the field label in any row
or column. If this is changed to a number, the text for the dropdown must reside on that row or
column only.

Test the Dropdown – After defining the dropdown, click the “Update Entry” button. This
records the changes to the list
shown during the dropdown
test.

When all adjustments have been made, click the “Done” button at the bottom of the screen to
store your changes.

7
 EXERCISE 2 - LOCAL DROPDOWNS

1) Click on the fpGIdev icon

2) Select the “Setup Configuration” button.
3) Click on the “Application Configuration Table” button
4) Select the “Drop Down List” tab.
5) a) Select a line from the browse list
b) Set enable to “True”
c) Enter the description of this dropdown as “Gender”
d) Enter the label for the Data Entry Field as “Sex”
e) The location of the label relative to Data Entry Field is “Left”
f) The file containing the dropdown entries is “C:\appl\office\sex.tx”
g) The number of lines to ignore at top of file is “0"
h) The title to be shown at top .... is “Code;Description”
i) Place a “0" in both the “Search Row and Col” fields
j) Click the “Update Entry” button
k) Repeat steps a-j using the following information:
Labels File
Eyes C:\appl\office\eyes.txt
Hair C:\appl\office\hair.txt
Race C:\appl\office\race.txt
Z, C:\appl\office\city.txt
? C:\appl\office\yesno.txt
6) Click the “Done” button at the bottom of the screen
7) Click on “OK”
8) Login to the client to see the changes you made.

8
 fileProGI ENHANCEMENTS - STATUS BAR

When you logon, the following menu will appear on your screen. These default menus use keys
that act like the character version. On the toolbar there is an “Options” menu. The “Show
images” option is checked in the application configuration.

While using this option you can:

1) Uncheck “show
images”causing the
background images to
disappear from the GIclient.

9
2) Uncheck “Show Menu
Action Keys.” This
leaves only the labels as
shown in the image to
the right. This is
especially useful for
those who don’t like the
single character key
association

3) Use templates which

have different
background and color
options.

10
When viewing a file, you will notice a different toolbar.

This is the date according to the client PC.

This is the disconnect button. Hopefully you will never need to use this; however, you
can use it to disconnect if the GIclient hangs and nothing else seems to work.

This is the button used

to print a hardcopy of
the screen. When
pressed, a preview
screen will appear.
After previewing the
image on the page,
select the “Print” button
at the left top corner of
the screen where the
normal Windows
printer selection dialog
box appears for
printing.

The Cut, Copy and Paste options for edit fields. The Ctrl-V option (for paste) and the
Ctrl-X option (for cut) work from the keyboard. However, the Ctrl-C option (for copy)
does not work because the GIclient uses the Ctrl-C option to cancel actions as the
character version does. Use Ctrl-Z to place the text back into a field if accidently
removed.

11
 Appearance Button - You will see the basic changes
associated with the screens; however, this option must be
enabled in the “Application Configuration” in order to show
on this toolbar.

Fonts and color for main form - Allows the user to re-map
the colors as mentioned in the developer section. As
previously stated, it is highly recommended not to adjust the
fonts. Adverse affects can occur.

Templates - These are the same background templates as used on the menus. The “Transparent
Background” must be unchecked. (See figure above.)

Browse Window - This is where you

adjust the browse window colors and
attributes. This is much like the
fonts and colors for the browse
screens; however, the selection bar
option is available. The default uses
the filePro colors.

Full Screen Background - will use the

top left corner color for the border.
If unchecked, it will use the gradient
colors around the borders from the
fonts and colors section.

Transparent Background - Currently,

“default” is checked. This allows
the filePro normal color mapping to appear. If unchecked, the template in use becomes the
background and the color mapping doesn’t appear. (See above figure.)

Cursor – allows you to use a blinking cursor much like that used in the character version. If
“show” is unchecked, the annoying little square cursor will disappear.

These buttons are associated with the filePro default

buttons on the bottom of the screen. The “X” is the
delete option, the printer will print a hardcopy of the
screen (character version), the diskette will record, the printer with Form is the F-Form option,
the magnifying glass will take you to browse mode, and Cancel is the Cancel option. The
Cancel option stays on the toolbar and runs unless “Break off/on” are set. If the button
disappears from the bottom of the screen, this option will work instead..

12
 SPECIAL FEATURES

In the update mode, there are several options available

within an edit field. They can be retrieved by a single right
click within the edit field. The first thing you will notice is
that the standard Cut, Copy, Paste and Select All commands
are available. There are a few other tools which are also
handy: Calendar,
Calculator, Colors, 3d
Borders.

1) The “Calendar” will take the date in an edit field and

show that date on the calendar. By clicking on a date,
the associated date is
returned to the field. The
single arrow buttons scroll between months while the double
arrows scroll through the years throughout the calendar.

2) The “Calculator” allows for simple calculation of

addition, subtraction, multiplication, and division. The
results are placed in the edit field.

3) The “Color” option allows you to change the highlight color (see the yellow area in the above
figure). The normal colors consist of the color of the edit boxes (see the white areas in the
above figures). The font should not be adjusted. The wrong size font can cause the
cursor position to disappear.

4) If “3D Borders” is unchecked, the screen will have a flat two-dimensional look in the edit
fields.

As mentioned before in the Developer section, these options can be turned off. Under the
“Application Configuration Table”, select the “Data Entry Screen” tab and click on the popup for
“Edit Fields” and set the options to “False” or add your own. I added the “Help” option <F10>.

13
 fileProGI - SHOW AND EDIT BUTTONS

FileProGI automatically converts the standard FilePro keys to action buttons usable by the click
of the mouse. User defined keys however need to be defined. The basic show button is one
where a single letter is the clickable label created with a simple show statement.

@entsel
show “\{0}-Screen 0, \{1}-Screen 1";end

Now let’s change the show statement to the Following:

@entsel
show “\{Screen 0:0} \{Screen 1:1}”;end

If you’d like an underline under the associated key use the &.

@entsel
show “\{Screen &0:0} \{Screen &1:1}”;end

The last two examples work fine on the GI clients, but the character clients have no way to
express the associated key in this manner. To solve this problem one can condition the show
command based on the “GUI” interface in use.

@entsel not GUI

show “\{0}-Screen 0, \{1}-Screen 1";end
GUI
show “\{Screen &0:0} \{Screen &1:1}”;end

Other uses of the show buttons are within inputs, input popups,
message boxes, etc.

Input ok(1,yesno) “Is this OK (\{Y}/\{N})?”

14
For special keys you can display them using something
like: \{F1 Key:[INSC]}

When using the GIclient, you will notice that some prior coding statements were passed over;
however, now they may be revealed. Some things to think about when creating buttons are
how and when they should appear. To make things easier a couple of flags, similar to -D, were
added to dclerk for execution.

These are:
-D While not new in 5.0 as the other -D type flags, this flag suppresses all the filePro
default buttons.
-DE This suppresses the default Delete, Hardcopy, Update, Exit, Print Form, and
Browse buttons, but leaves the default buttons in update mode as Record, Cancel
and Browse Lookup. This flag is useful when the button descriptions exceed the
one show line or you want the description of the default buttons changed.
-DU This flag suppresses the default buttons in update mode, such as Record, Cancel
and Browse, leaving the Delete, Hardcopy, etc. buttons when not in update mode.

Example of command on menu: /fp/dclerk demo -s0 -DE

1) With the definition of these buttons, what happens when one goes into update mode, using the
examples above?

Answer: The Screen 0

& 1 stay on the screen.

2) How do we solve this problem? Simply add this to your input processing table.

@update If:
Then: show "";restart

The results should now

appear in update mode now
as seen to the right.

15
Edit fields can be made into buttons in a similar manner. To accomplish this, make sure the
“Suppress Status” check box in the Application Configuration is unchecked.

Make the following edit field in demo:

SEX '\{M:M:Male}-Male \{F:F:Female}-Female' ^~ "M" | "F"

With the “Suppress Status” box in the “Application Configuration” checked, the line with the
“Male” and “Female” buttons will not appear, nor will anything else send to this line, such as the
“next match” button in index mode. You do not have to worry about losing command ordinated
text, since this line is not beyond the normal filePro display.

16
 NEW MESSAGE SEND COMMAND

There are several client side functions which can take place in GI. For these to be accessed, the
program must be setup with the new message command. This command only has to be executed
once in order to initialize, and then can be called throughout the processing.

@once If ‘ *** first a variable must be defined

then Declare global menucall(8,.0,g)
If
then menucall=new message ();end

From this point the Message command can call client side commands. Place the above
processing within the input processing table. Now that we have the variable defined, let us
enable some of the GI features. All messages are sent through the Message menucall SEND
“(@...@)” type format.

BUILT-IN VIEWING

There is built-in viewing available in the GIclient. Using this viewer, one can bring up images
and text files local to the client (map drives included). These file types must end in txt, jpg or
bmp (see the following examples). In order to see a picture appear whenever you hit the F8 key
within a field, type the following within your processing table. (Remember the @once
processing mentioned above is required for this to work.)

@wuk*

If
Then Message menucall SEND “(@D,1,1,C:\ “{“appl\ “{“office\ “{“photos\ “{“pic2.jpg@)”
If
Then end

Notice that we had to use space quote left curly bracket

quote to avoid the letter following the backslash being
considered literal.

17
In order to view a read-only note, enter the following to bring up a text notation with the included
viewer.

@keyn
If ‘ **** the 1,1 represent the starting row and column for display
Then Message menucall SEND “(@D,1,1,C:\ “{“appl\ “{“office\ “{“note.txt@)”
If
Then end

If you wish to have the processing close the

viewer, it is possible to use the message
command as follows:
Message menucall SEND “(@X,1@)”

EMBEDDED FILES/GRAPHICS

The built in viewer is nice, but what if you

want your images to appear as part of the
screen? There is an available option for this
as well. However, before doing this it is
recommended to have a cleared-off section
of the screen to view the image. Otherwise
screen edit fields will not show up.
Secondly, once an embedded image is
called, it will not disappear unless you exit
that dclerk session, you call another image,
or you tell it to disappear.

18
Take a look at screen 1 of the demo example. Notice
there is a big clear space on the right hand side of the
screen. This is where we will place the pic2.jpg image
we used in the viewer example. As always with these
calls the @once processing in exercise 2 must first be
within our processing table.

The format is (@E,filename,start row, start column,

width, height@).

@keye If
Then
Message menucall SEND "(@E,C:\ "{"appl\ "{"office\ "{"photos\ "{"pic2.jpg,1,45,40,18@)"
If:
Then: end

Now to close the embedded image use the following type of process:

@keyc If
Then: Message menucall SEND "(@EX@)”;end

You may have noticed that the image

was larger than the assigned viewable
area. One way to solve this problem is
to view the image from an html page.
Type the following lines into your input
processing table and then exit out to
view the image.

@keyg If ' display embedded image through Html

Then:
Message menucall SEND "(@E,C:\ "{"appl\ "{"office\ "{"photos.htm,1,45,40,18@)"
If
Then end

19
 LAUNCHING CLIENT SIDE APPLICATIONS

Client side applications can easily be launched within GI. For launching web sites or emails it
can be as simple as a showing statement on a
screen and clicking the name:

Example:
@keyw If
Then Show “@Go to Web site www.henschen.com”;end

@keym If
Then Show “@Email me at [email protected]”;end

The main power comes from the

(@R,filename,Params@) option of the new message
command. By using this, one can execute any client
side application, as long as you know it’s executable.
With the @once processing mentioned above, here are
a couple of examples of running applications from the
client. Taking the same pic2.jpg file we used in
Example 3 and 4, bring it up in the viewer for the jpg
extension type.

@keyr If
Then Message menucall SEND "(@R,C:\ "{"appl\ "{"office\ "{"photos\ "{"pic2.jpg,@)"
If
Then end

The same is true with txt, doc extension:

@keyt If
Then Message menucall SEND "(@R,C:\ "{"appl\ "{"office\ "{"note.txt,@)"
If
Then end

20
Now let’s proceed a step further, by creating a WordPerfect Merge. To accomplish this we need
three things: 1) A WordPerfect form to merge with - for our example we will use demo.frm; 2)
A macro which merges the data to the form (demo.wcm); and 3) A Filepro Output “processing
only” form (demo_w) which creates
the ASCII string and executes the
macro. We are going to create the
filePro processing and use the existing
WordPerfect document and macro.
The following is a simple export ASCII
command followed by the execution of
the macro demo.wcm. In order to run
the macro, you need to run the
following from the Windows start run:

subst U: c:\appl\office\class

This creates a drive U: from the directory c:\appl\office\class. For networks, you would simply
map drive U: to the servers \appl\office\class directory.
-------------------------------------------------------------------------------
1 ------- - - - - - - - - - - - - - - - -
If:
Then: '********** WordPerfect Data ****
2 ------- - - - - - - - - - - - - - - - -
If: ' define variable for ascii export
Then: declare wpdata
3 ------- - - - - - - - - - - - - - - - -
If: ' Set path for ascii export fplogin internal variable giserver
Then: wpdata="C:\ "{"appl\ "{"office\ "{getenv("FPLOGIN"){"\data.wp"
4 ------- - - - - - - - - - - - - - - - -
If:
Then: export word field=(wpdata)
5 ------- - - - - - - - - - - - - - - - -
If:
Then: ' Fields Used in string
6 ------- - - - - - - - - - - - - - - - -
If:
Then: field(1)=1
7 ------- - - - - - - - - - - - - - - - -
If:
Then: field(2)=5

21
 8 ------- - - - - - - - - - - - - - - - -
If:
Then: field(3)=12
9 ------- - - - - - - - - - - - - - - - -
If:
Then: field(4)=13
10 ------- - - - - - - - - - - - - - - - -
If:
Then: field(5)=10
11 ------- - - - - - - - - - - - - - - - -
If:
Then: aa=instr(52,"1","1")
12 ------- - - - - - - - - - - - - - - - -
If:
Then: field(6)=mid(52,"1",aa-"1")
13 ------- - - - - - - - - - - - - - - - -
If:
Then: field(7)=53
14 ------- - - - - - - - - - - - - - - - -
If:
Then: field(8)=39
15 ------- - - - - - - - - - - - - - - - -
If:
Then: field(9)=38
16 ------- - - - - - - - - - - - - - - - -
If:
Then: field(10)=50
17 ------- - - - - - - - - - - - - - - - -
If:
Then: field(11)=6
18 ------- - - - - - - - - - - - - - - - -
If:
Then: field(12)=7
19 ------- - - - - - - - - - - - - - - - -
If:
Then: field(13)=8
20 ------- - - - - - - - - - - - - - - - -
If:
Then: field(14)=25
21 ------- - - - - - - - - - - - - - - - -
If:
Then: field(15)=""

22
22 ------- - - - - - - - - - - - - - - - -
If:
Then: field(16)=""
23 ------- - - - - - - - - - - - - - - - -
If:
Then: write field;close field
24 ------- - - - - - - - - - - - - - - - -
If:
Then: Message menucall SEND "(@R,C:\ "{"appl\ "{"office\ "{"demo.wcm,@)"
25 ------- - - - - - - - - - - - - - - - -
If:
Then: end
26 ------- - - - - - - - - - - - - - - - -
@once If:
Then: declare global menucall (8,.0,g)
27 ------- - - - - - - - - - - - - - - - -
If:
Then: menucall=new message ()
28 ------- - - - - - - - - - - - - - - - -
If:
Then: end
29 ------- - - - - - - - - - - - - - - - -
Explanation of Code:
Line 2: Declares a variable to use for the directory path
Line 3: This line defines the path and name of the exported file. Notice the
getenv(“FPLOGIN”). Getenv(“FPLOGIN”) is referring to a GI server
variable of how the user logs in. This is platform independent, so even
though there is no @id in the Windows version, one can use this variable
in its place. Using this type of file structure allows us to keep each
individual’s data separate from another. From this location, the client can
map a drive letter to their log-in location, giving the ability to address the
same location for all users’ macros.
Line 4: Setting up the export for comma delimited ASCII.
Lines 5-22: Assigns the filePro field to its position within the ASCII string.
Line 23 Writes and Closes the ASCII string. This must be done so the data
becomes a file prior to the form finishing. Forgetting this can cause
improper data or no data from getting to the document.
Line 24: The message SEND command. The C:\appl\office\demo.wcm is referring
to the macro wishing to execute from the GIclients reference.
Line 25: Terminates the processing
Line 26: Sets up the processing which runs once to setup the messaging to the
GIclient. Sets up the long dummy variable for the message handle.
Line 27: Assigns the message handle to the variable menucall

23
 ADDITIONAL MESSAGE SEND OPTIONS

Now that you have your dropdowns and buttons create, let’s go over some other message send
options. As mentioned in the viewer section, the @once processing must be setup for these to
work:

@once If:
Then: declare global menucall(8,.0,g)
28 ------- - - - - - - -
If:
Then: menucall=new message ()
29 ------- - - - - - - -
If:
Then: end

(@P,pathname@) Sets a Global pathname that can be used for the client when defining
locations.
(@P,@) Clears the pathname

This is a very useful message. Let’s say you have an application which uses various codes for
filings. Although the same dropdown description (“entry”) is on each file screen, you want
different context depending on the “filePro file”. You must set up the dropdown as described
on page 6. However, in the file containing the dropdown entries, change the “full path to file”
(literal path) to:

C:\appl\office\$path\entry.txt

Create two text files called “entry” and place them in directories C:\appl\office\{your ”filePro
file” names}. Now when you set the Message send command to the {“filePro file” name} the
$path will be replaced with the {“filePro file” name}. This might be within the @once
processing routine. Example of setting demo to the path:
27 ------- - - - - - - - - -
@once If:
Then: declare global menucall(8,.0,g)
28 ------- - - - - - - - - -
If:
Then: menucall=new message ()
29 ------- - - - - - - - - -
If:
Then: Message menucall SEND "(@P,demo@)"
30 ------- - - - - - - - - -
If:
Then: end

24
Display a Dialog Box (@DLG,box-type,buttons,text-of-message@)

The “box-type” is an integer and selected from the following:

1 - Warning A message box containing a yellow exclamation point symbol.
2 - Error A message box containing a red stop sign.
3 - Information A message box containing a blue "i".
4 - Confirmation A message box containing a green question mark.

Clickable message buttons (comma “,”delimited) can be created by setting 1-> on, 0-> off.
Button Descriptions are listed below and must follow the order shown below.

Button Descriptions
1 - Yes A button with a green check mark and the text 'Yes' on its face
2 - No A button with a red circle and slash mark through the circle with ‘No’ on its face.
3 - OK A button with a green check mark and the text 'OK' on its face
4 - Cancel A button with a red X and the text 'Cancel' on its face
5 - Help A button with a cyan question mark and the text 'Help' on its face
6 - Abort A button with a red check mark and the text 'Abort' on its face
7 - Retry A button with two green circular arrows and the text 'Retry' on its face
8 - Ignore A button with a green man walking away and the text 'Ignore' on its face
9 - All A button with a green double check marks and the text 'All' on its face

e.g., (@DLG,3,0,0,1,0,0,0,0,0,0,File Not Found @);

This would display an Information dialog

box (3 above) with an OK buttons (3rd digit
set to “1") displaying “File not Found” text.

The dialog boxes are always displayed

modal, so the user must respond to it
immediately.
If the dialog box window is “X” closed
directly, it is equilavent to clicking on the
“Cancel” button. Please note the button
clicked is NOT passed back to filePro for
evaluation.

Example:
If exists ("V:\photos\demo\ "{50{".jpg")ne "1"
Then: Message menucall SEND "(@DLG,3,0,0,1,0,0,0,0,0,0,No File Exist for"<50{"@)";end

This would display an INFORMATION dialog box with OK text button, with a “NO FILE
EXIST” message.

25
 MISCELLANEOUS CHANGES

Notice that my splash screens have our company

logo on them and not the filePro Trade Mark.
To change the filePro Splash screen, go to the
~\fp\fpGIdev\runfiles directory. In this
directory you will find a file called
IntroImage.bmp. This file, if you maintain it’s
size and format, can be changed to be your
introductory screen with most paint programs.

Now let’s look at the screen you receive if you

exit without logging in. This background can
be changed as well in the same runfiles
directory. This image name is called
Splash.bmp. Have fun adding your own.

If you are familiar with html coding you can

perform minor changes to the default menus,
which come up. However, it would be wise to
make backup copies before making any
changes to these files. Within the
~\fp\fpGIdev\runfiles directory notice two files:
MenuTemplate1col.htm
MenuTemplate2col.htm.
With slight modifications, the non-filePro
related links can be changed to link to other
items or images using a text editor. Instead of
going into detail, here are a couple of examples
one could use.

26
1) < a href="\documents\example.doc#EXTERNAL">

This would bring up the “ \documents\example.doc” in the default Window application

associated with the 3 character extension. Example: “.doc”
This could be used for an “on-line help” manual system.

2) <a href="http://henschen.com">

This brings up an external html browser and goes to the site mentioned. Great to point
users to your site for updates, etc.

3) <a href="mailto:">

This brings up the Windows mail program. Following the mailto: one could add an
email
address. Example mailto:[email protected].

These changes become universal, in that all menus have the same linking information. Please
note that this is a very basic Browser used for the menus. Java and some html codes do not run
with this environment.

27
 MISCELLANEOUS CHANGES

Notice that my splash screens have our company

logo on them and not the filePro Trade Mark.
To change the filePro Splash screen, go to the
~\fp\fpGIdev\runfiles directory. In this
directory you will find a file called
IntroImage.bmp. This file, if you maintain it’s
size and format, can be changed to be your
introductory screen with most paint programs.

Now let’s look at the screen you receive if you

exit without logging in. This background can
be changed as well in the same runfiles
directory. This image name is called
Splash.bmp. Have fun adding your own.

If you are familiar with html coding you can

perform minor changes to the default menus,
which come up. However, it would be wise to
make backup copies before making any
changes to these files. Within the
~\fp\fpGIdev\runfiles directory notice two files:
MenuTemplate1col.htm
MenuTemplate2col.htm.
With slight modifications, the non-filePro
related links can be changed to link to other
items or images using a text editor. Instead of
going into detail, here are a couple of examples
one could use.

26
1) < a href="\documents\example.doc#EXTERNAL">

This would bring up the “ \documents\example.doc” in the default Window application

associated with the 3 character extension. Example: “.doc”
This could be used for an “on-line help” manual system.

2) <a href="http://henschen.com">

This brings up an external html browser and goes to the site mentioned. Great to point
users to your site for updates, etc.

3) <a href="mailto:">

This brings up the Windows mail program. Following the mailto: one could add an
email
address. Example mailto:[email protected].

These changes become universal, in that all menus have the same linking information. Please
note that this is a very basic Browser used for the menus. Java and some html codes do not run
with this environment.

27
Variables and Pitfalls of GI

the cls command has to be on a line of it’s own or else the show on statement on the line is
cancelled when an additional show command is issue. Ex:

IF: GUI
Then CLS
IF: GUI
Then: showctr(“22") “\rH\r-Hardcopy, \rX\r-Exit”
IF: GUI
Then showctr(“23") “\rI\r-Image, \rF\r-Forms”

Server Side (Config Variables):

Local Printing within the Giclient works with the new windows version of Filepro/GIclient
combo

set PFPT=on
set PFPRTC=hplaser

The Autogoto warning that comes up when the cursor can’t reach the distanation of the mouse
click can be surpressed with the variable:

set PFAUTOGOTOWARN=off

Turns of the cursor Path logic on the Giclient to quickly skip to the entry field. If this is set to
off any @wlf/@wef logic in between the location the cursor leaves and goes to isn’t honored.

set PFFORCECURSORPATH=off

other variables that may be of interest include PFEDFAILBOX, PFLOCKBOX,

GISERVER

On Unix servers if the current time coming up with the colon is off by server hours, one may
have to set the TZ variable within the ~/fp/giserver/lib/giserver.cfg.
GIClient

If you desire to change the title on minimized program name and title bar, one can use the title
option upon execution. This way one could have different applications icons executing the same
program with different titles. First create a shortcut of the fileproGI executable. Then go to
properties and add to the target line.

Change: fileproGI.exe
To: fileproGI.exe “title=My Title”
Creating Buttons in
fileProGI
 filePro components

! Show statements
< These statements allow you to display messages, letters
or buttons at the bottom of the screen.
! Gui/Not gui statements
< These statements allow filePro to distinguish between
graphical commands and character commands.
! Inverse Brackets (\{text goes here})
< These highlight the text that is in between them. For
graphical, they give the appearance of a button. In
character, they only highlight the text.
 Show statements

------------------------------------------------------------------------
If:
Then: show “This centers at the bottom of screen”
------------------------------------------------------------------------
If:
Then: show (”1",”5") “This shows at position indicated”
------------------------------------------------------------------------
If:
Then: showctr (”22") “This centers on that specific line”
------------------------------------------------------------------------
 Gui/Not gui statements

--------------------------------------------------------------------
If: not gui
Then: show “If character, then show this”;end
--------------------------------------------------------------------
If: gui
Then: showctr (”22") “If graphical, then show this”;end
--------------------------------------------------------------------
 Inverse Brackets

-------------------------------------------------------------
@entsel If: not gui
Then: show “\{A}-Address”;end
-------------------------------------------------------------
If: gui
Then: showctr (”22") “\{Address:A}”;end
-------------------------------------------------------------

@entsel tells filePro that you

want this to popup “at when
entering selection/record”
 How to Create Buttons

! One Letter Button

! Full Word Button
! Full Word Button with corresponding letter
underlined
 One Letter Button

------------------------------------------------------
@entsel If:
Then: show “\{A}-Address”;end
------------------------------------------------------
If there is no condition as to whether it is to be
used in graphical or character, it will display the
same in both. However, in graphical it will be a
clickable button, while in character it will just be
the highlighted letter of the function.
 One Letter Button
Graphical look:

Character look:
 Full Word Button
----------------------------------------------------------------
@entsel If: gui
Then: showctr (”22") “\{Address:A}”; end
----------------------------
The “ : ” lets filePro know the
corresponding key associated with
the button.
filepro also has special keys that can be made into
buttons:
-------------------------------------------------------------
If: gui
Then: showctr (”22") “\{\K4:[SAVE]:Record}”
-------------------------------------------------------------
 Full Word Button
Character look:

The reason you don’t use

this in character is
because you can’t really
see what letter to press to
start that function.
 Full Word Button
Graphical look:

Delete, Hardopy, Update, Exit,

Print Form, and Browse are all
standard functions/buttons in
filePro.
 Full Word Button With
Corresponding Key Underlined

The “&” creates the underline under the letter that it is next to.
Which should always be the corresponding key stroke on the
keyboard for that function. (GI only)
---------------------------------------------------
@entsel If: gui
Then: show “\{&Address:A}”;end
---------------------------------------------------

filePro looks for the

“@keya” processing to
run the function.
 Full Word Button With
Corresponding Key Underlined
Graphical look:

This lets the user know if

they press the letter “A”
on the keyboard, then it
will run the same function
as if they used their mouse
to click on the Address
button.
 Menu Command Options:

1. -d (update mode & @entsel access)

a. Gives full access (no standard buttons are displayed in update
mode or @entsel)
2. -de (@entsel access)
a. Gives access only at @entsel command. In update mode, the
standard functions/buttons are displayed.
3. -du (update mode access)
a. Gives access only when in update mode. At @entsel, the
standard functions/buttons are displayed.
 Additional Button Information
(hints & tips):

Input/input popup statements:

-------------------------------------------------------------------------------------------------
If: gui
Then: input popup za(1,allup) “Please select button: \{One:1} or \{Two:2} “
-------------------------------------------------------------------------------------------------
 Additional Button Information
(hints & tips):
In GI, edits can be made to be a clickable button as well:

Define Edits:
---Name-- ----------------------- Edit ----------------------
avd .’\{Add:A} \{View:V} \{Delete:D}’ {~”A”|”V”|”D”}
 Additional Button Information
(hints & tips):
Tip: when using a button on the bottom of a screen, if the
function is an “@key” process and it calls for one to add,
view, or delete, here is a shortcut:
*instead of giving the option of add, view or delete, just
automatically start the function in view mode and then add
the buttons for add and delete once in the browse mode:
Additional Button Information
(hints & tips):
 Dropdowns in filePro

! Set a standard for your dropdowns.

! Set up screens for GI.
! Create dropdowns in toolkit.
! Insert appropriate dropdown codes to screens.
! Check screens for overlapping fields.
! Dropdowns in forms and reports.
 Setting Standards for Dropdowns

! There are several options when determining

dropdowns.
P The word by itself.
N Hair
P Punctuation.
N ?
P Combination of both.
N Race,
 Setting Up The Screens for GI

! Remove any unnecessary punctuation from

screens through Define Screens.
! If using color on the first line of screen, you
must remove the color in field (1,1).
! Adjust the fields to create a “clean” look to the
screen.
 Border Color

Color Determines border on

position (1,1)
 Create Dropdowns in Toolkit

! Text files are static files local to the GIclient.

< The column fields in the file are separated by semi-
colons (;) by default.
< After updating the text in the dropdown the results do
not appear until the GIclient is exited and login again.
! They could also be stored on a mapped network
drive.
 Insert Appropriate Dropdown Codes

! Insert the codes onto the screen.

! When adding a dropdown, you will need to
leave additional space so the dropdown will not
overlap the next field or description.
 Dropdowns Used in Forms & Screens
! For more user friendly prompts, change input
statements to read “input popup” when
prompting for infomation in forms and on
screens.
If:
Then: input za(20,uplow) “Dissolution Granted:”
--------------------------------------------------------------------------------------------
If:
Then: input popup zb(10,mdyy/) “Date Dissolution Granted:”
--------------------------------------------------------------------------------------------
If:
Then: input popup ok (1,yesno) “Continue?:”
----------------------------------------------------------------------------
 Forms and Reports
! Remove all unnecessary puncutation at the end
of the input statement.
! Leave a space between the last character of line
and the end quotation.
If:
Then: input popup za(20,uplow) “Dissolution Granted ”
--------------------------------------------------------------------------------------------
If:
Then: input popup zb(10,mdyy/) “Date Dissolution Granted ”
--------------------------------------------------------------------------------------------
If:
Then: input popup ok (1,yesno) “Continue ? ”
----------------------------------------------------------------------------
fileProGI and Toolkit

Training In Orlando

October 2003
 What’s In the Toolkit?
! Additional appearance controls for GIclients
< Suppressing Status Buttons
< 3D protection fields
< Enable the “Appearance Button” in data entry
screens for color mapping in the GIclient.
< Add and subtract information from popup menus
< Activate the GIclient messaging commands
! Dropdown definitions enabling
< Based on screen information, create drop downs
using text local files.
 Configuration
GIclient Toolkit
 Dropdown Listing
File containing
dropdown definitions.
When associated with
the Vrbl Name can be
Name referenced in the used to call additional
message send command dropdown list in
for alternate dropdown conjuction with the
list (@LDD,extra2) default list
Changing Dropdown List Definition File Name

Double Click this location

will allow one to change the
name of the file used to
define dropdowns
 Debugging Enabled

Sets the debug logging

for the Giclient
~/fileproGI/fileproGI.#.
#.#.#.dat
Suppresses FP Edit
prompts from
displaying on data
entry screen

Unchecked

Checked
 Beveled Protection Fields

Checked

Check to give protected

field 3D look, uncheck
to appear as part of
text screen.

Unchecked
Appearance Button on DataEntry Screens

Checked
Places appearance
button on the
GIclient screen for
end user to make
adjustments to
screen color and
characteristics.

Unchecked
Menu Screen Detail

Check if you want Fpmenus

to pass keystrokes to server,
otherwise mouse clickable
only.

Default folder for html menus,

anything called in processing
will append to this location.
Menu Action Key

Action Key

No Action Key
Dropdown Menu on FP Menus

Define Dropdown
Menu Options For FP
Menus, Like the F10
Help.
Data Entry Screen - Font Use

The name placed in

theToolkits Titlebar
When unchecked end
of edit fields will
appear to be longer
then amount of data
they can contain.
 Setup Colors and Fonts

Using the PFTERM=cansi

or ansic, and based on
Termial Color allows color
mapping for Unix sytems
Changing Colors
Review Character Screen
Associate different Foreground (text) and
Background Colors to the GIclient Screens
After Color Adjustments
 Clickable Addresses

Allows web addresses

within show, msgbox, etc
when clicked to open the
default browser and go
to the site.

Allows E-Mail addresses within show,

msgbox, etc when clicked to open the
default mail program.
Field Highlight When Entered

Checked to Automatic
Highlight data

Unchecked to not
highlight data when
entering field
Dropdown Menus on Screens

Right Click to test

dropdown menu
 Images/Text Base Path Location

When using a path

here any addressing
of the image name is
appended to this
location.
 Changing IP and Port Address on
GIclient
Edit the list of Servers with the associated IP addresses by clicking
the folder icon.

Port address can be

specified by adding a
colon and the port
number after the IP
address.
 Configuration File – fpgiConfig.dat
Once all changes have been made to the Toolkits Application
Configuration Table. One clicks the Save Configuration Button. This
places a file ~\fpGIdev\ConfigFile\fpgiConfig.dat on the toolkits
system. Copying this file with the fileproGI.exe file from the GIclient
creates a Giclient with the modifications performed in the Toolkit.
 Title Flag to Run GIclient

The fileProGI.exe can be executed with the

“Title” option. One can setup several
shortcuts to reflect different Titles with the
same execution.

fileProGI.exe “title=My Title”

To do this:
! Right click on the FileproGI shortcut on the desktop
! Select Properties
! Add to the end of the Target the “title=My Title”, where My
Title is the beginning label of the titlebar and minimized titles.
 New FP Enviromental Variables
! PFPT=on – Local printing to GIclient added to Windows Giserver
! PFPRTC=printer_code – Local print codes added to Windows Giserver
! PFAUTOGOTOWARN=off – Removes the warning relating to a mouse
cursor location could not be reached. This is caused from an interruption
due to a popup, input, or other user prompt request, or the cursor returns
to the position it left from. If set to “off” no warning message appears.
! PFFORCECURSORPATH=off – Turns the cursor pathing off,
preventing @wef/@wlf processing not to be honored and skips directly to
the location.
 Enviromental Variables used for
Cleaner Presentations
! PFEDITFAILBOX=on – Edit Failed messages appear in a
box in the center of the screen instead of the bottom.
! PFLOCKBOX=on – Flashes Record Being updated Message
! TEXTNORMAL, TEXTINVERSE, DIALOGNORMAL,
DIALOGINVERSE, POPUPNORMAL, POPUPINVERSE,
ERRORNORMAL, ERRORINVERSE, HELPNORMAL,
HELPINVERSE – Sets Colors for screen when used with
proper TERMCAP, (ex: cansi/ansic – Unix)
 Quick Changes

! Show Buttons
! Drop downs added to screen
! Web page/email launching from a show, or msgbox
command
< show “@Click email address: [email protected]”
< Msgbox “Click and go to www.domain.com”
 Message Send Command
! Message Send Commands are the means for filePro to
communicate to the GIclient to execute local applications
and commands.
! All Message Send Commands must declare a handle
! Most Message commands have the syntax:
< Message handle SEND “(@option,....@)”
! Message Send Commands Only work on License files
received from a party with the Toolkit.
< If one purchases the toolkit directly
< If a Developer has purchased a toolkit and license their
customers GIclients.
 Current Message Commands
! Read-Only Display @D
! Embedded Files/Graphics @E
! Running Giclient side Applications @R
! Alternative $path value @P
! Secondary Dropdown Descriptions @LDD
! Dialog Box @DLG
 Display Message Commands
! Read-only Display (@D,r,c,file@) (@D,r1,c1,file1,r2,c2,file2@)
< Files consist bmp, jpg, and txt files
< Though two display files can be told to come up from one
message send. One can’t just address file2 in the manner
(@D,,,2,3,file2@)
< There is no sizing parameters, so it takes on the resolution of
the image or file in the built in viewer.
< One can resize and move the window for the period of time the
display is up and return to original size and location when
executed.
< Can be closed by either the by right corner X or using the
(@X,1@) (@X,1,2@) message send option
35 ------- - - - - - - - - - - - - - - - -
@keye | If: ' display embedded image
Then: Message menucall SEND "(@D,1,1,C:\ "{"appl\ "{"note.txt@)"
36 ------- - - - - - - - - - - - - - - - -
| If:
Then: end
37 ------- - - - - - - - - - - - - - - - -
@keyc | If: ' close embedded image
Then: Message menucall SEND "(@X,1,@)"
 Embedded Files/Graphics

! Files can be html, jpg, bmp (@E,File,r,c,w,h@)

< Where character position r=row,c=column,w=width,h=height is
the borders of the File
< If File is beyond the specified borders, a scrollbar appears
< Once up an image changes only after execution of another image
or “close” message (@EX@)
< Best used on screens with a cleared location.
< When used with an input statement a html type file can be used as
a menu selection. Ahref uses “sendfieldleavemsg=”
35 ------- - - - - - - - - - - - - - - - -
@keye | If: ' display embedded image
Then: Message menucall SEND "(@E,C:\ "{"appl\ "{"office\ "{"photos\ "{"photos\ "{"pic2.jpg,1,45,40,18@)"
36 ------- - - - - - - - - - - - - - - - -
| If:
Then: end
37 ------- - - - - - - - - - - - - - - - -
@keyc | If: ' close embedded image
Then: Message menucall SEND "(@EX@)"
38 ------- - - - - - - - - - - - - - - - -
| If:
Then: end
 Running GIclient side Applications

! Allows for the launching of local applications (@R,file,param@)

< Where file is any file addressable from the client.
< If the param is left off, it will execute using the default
application for the file extension.
< These can include Merges with the use of mapped drives
47 ------- - - - - - - - - - - - - - - - -
| If: ' Run windows application associated with jpg
Then: Message menucall SEND "(@R,C:\ "{"appl\ "{"office\ "{"photos\ "{"photos\ "{"pic2.jpg,@)"
45 ------- - - - - - - - - - - - - - - - -
@keyr | If:
Then: Message menucall SEND "(@R,C:\ "{"WINNT\ "{"system32\ "{"mspaint.exe,C:\ "{"appl\ "{"office\ "{"photos\ "{"pic2.jpg@)"
 Path Messages @P
! Alternative $path value (@P,location@)
< Used to replace the value of $path with the location value.

Address Book

Customers Vendors

/textfiles/$path/address.txt

/textfiles/customers/address.txt /textfiles/vendors/address.txt
 Dialog Box @DLG

! Format (@DLG,box-type,Button,text-of-message@)
! For Information Use only at this time.
! Requires User to close, before continuing on.
< Box Types:
1) Warning – Yellow Exclamation Point symbol

2) Error – Red Stop Sign

3) Information – Blue “I”

4) Confirmation – Green question mark

 Dialog Box @DLG

! Format (@DLG,box-type,Button,text-of-message@)
< Buttons are setup in a binary series of 1(on) and 0 (off) with
the list below.
< Buttons:
1) Yes
2) No
3) Ok ------ - - - - - - - - - - - - - - - -
| If:
4) Cancel Then: message menucall SEND "(@DLG,1,1,1,1,1,1,1,1,1,1,Warning Dialog Box@)”
------ - - - - - - - - - - - - - - - -
5) — Unused —
6) Abort
7) Retry
8) Ignore | If:
Then: message menucall SEND "(@DLG,2,1,1,0,0,0,0,0,0,0,Error Dialog Box@)”
9) All
 Things Henschen & Associates Has Done
! Word /WordPerfect Merges
< Export Data from filePro using jsfile or export command
< Run Macro Merge document
! Photo List and Copy Routine
< Collect Directory file Information
< Writes html using jsfile command
< Embedded Display list
! HTML Menus
< Executed from startcmd
< Ahrefs are setup to “send” the results to command prompt
! HTML Scheduler
< Using HTML frames ahrefs pass results to dreport to generate next
page.
 GIadmin

! User Accounts
< Delete add and change GI accounts
< See associated processes of user
! Administer several servers from a single location
< Shutdown Clients
< Check logs
! Configure new servers
! Shutdown remote GIserver
 GIadmin -- Select Server
Servers configured
for Giadmin to login
to.
Remote Shutdown
of GIserver logged Disconnect the
in to for GIadmin from the
administration. logged in toGIserver.

Closes GIadmin
GIadmin – Edit
 No Login

Check Filepro
Giclient IP/Port
Character and GI
Address
versions

Giserver
Running?
Giserver.lic in
Java Install and ~/giserver/lib
Path Set? licensed for this
server?
Check Log
Giserver.err
~/giserver/logs/

Call
Support
 Determine filePro Versions
< GIclient can be obtained by either clicking on the
login logo, or Help -> About from the titlebar menu
after logging in.
< GIserver – ~/fp/giserver/giserver -ver
< GIadmin – Under help about of the GIadmin toolbar
menu
< Runmenu – On character menu hit Shift-Tab
< D/Rclerk – set the PFVER=on and look in the upper
right corner of the Inquire/Update/Add from the Main
menu.
< D/Rreport – set the PFVER=on upper right corner of
Request Output menu item.
 GIserver Running

! Unix: (For Unix giserver to run properly both lserv and giserver.jar
processes must be running.)
< # ps -ef|grep giserver.jar
< # ps -ef|grep lserv
< If not running execute ~/giserver/start
! Windows:
< Go to the Task Manager
< Processes Tab and look for jsl.exe
< If not running execute the giserver from Services
 Java Install and Path Set (Windows)
! Windows:
<~\fp\jsl\bin\jsl.ini [java] section match the file Location
[java]
params=4
param00=-cp
param02=com.fptech.giserver.Server
param03=%1
jrepath=c:\appl\fp\jre1.4.1
wrkdir=c:\appl\fp\giserver
param01=c:\appl\fp\giserver\giserver.jar
 Java Install Path Set (Unix)
! Locate the Java Program (version 1.2 and above)
< java -version -or- pkginfo -x|grep java
< Most located under either /usr/java2/bin or /usr/jre2/bin
< Set pathing in the /etc/profile –
PATH=/usr/java2/bin:$PATH;export PATH
! If Java isn’t installed a copy can be downloaded at www.fptech.com
under the download link, or by the vendors site.
! ~/giserver/giserver.sh files path should match the java location.
 Licensed for Server

! ~/giserver/lib/giserver.lic # more giserver.cfg

< File generated from www.fptech.com serverName=uw8

debug=false
recall=1
P Requires Mac address from primary card expire=180
idleout=0
N Unix: ipconfig -a address follows the label port=4350
licensePort=4550
“ether” exec=/appl/fp/fpdaemon_sco
N Windows: ipconfig /all address follows the adminName=chris
log=true
Physical Address Line. logconnections=true
logPrograms=true
P Windows has machine name option logHeartbeat=true
logAdmin=true
N From command prompt directory listing (dir /w /p) forcePassword=false
adminPort=4450
the Six Alpha characters following the Serial serverAddress=172.16.0.1
Number. timeout=3
shutdownOnExit=true
! Check ~/giserver/lib/giserver.cfg file for the Port password=M-`M-n gM-\M-x~M-^I~M-a
remoteShutdown=true
number is consistent to the requested license.
(Default: Port=4350)
 Check GIserver.err Log

! Reviewing the giserver.err log can often reveal the problem

related to giserver stopping.
< ~/giserver/logs/giserver.err

Fri Aug 15 07:41:29 EDT 2003 Gethost library not found. Using license server ins
tead.
Fri Aug 15 07:41:30 EDT 2003 MAC addresses found 00c00d00dcce 000000000000 00000
0000000^@
Fri Aug 15 07:41:30 EDT 2003 3 addresses were return for validation check.
Fri Aug 15 07:41:30 EDT 2003 Checking license for MAC address 00c00d00dcce
Fri Aug 15 07:41:30 EDT 2003 Comparison of 00c00d00dcce to 00c00d00dcce suceeded.
Fri Aug 15 07:41:30 EDT 2003 License validated using MAC address
No Menu After Login

~/fp/fpdaemon_sco
permissions to
execute

Users account
information setup proper

Check Log daemon2.log in

/tmp or X:\daemon.log

Number of
Processes
exceeded nproc

Call
Support
 No Menu After Login
!Most cases after an install where all users can’t login, it’s due to
fpdaemon_sco not being executable.
!Check ~/giserver/lib/giserver.cfg
< exec=/appl/fp/fpdaemon_sco line consistent with fpdaemon_sco
location. (Fpdaemon_win/fpdaemon_NT for windows platforms)
< Recheck your license port is the same as requested (default 4350)
!Check Log /tmp/daemon2.log (Unix) or X:\daemon.log (Windows)
--- fpdaemon started ---
Date: Mon Sep 22 14:50:59 2003

[0] = '/appl/fp/fpdaemon_sco'
[1] = '/appl/fp/runmenu'
[2] = 'dpromenu'
!Number of Processes used may need increased if several have logged
in and no additional users can. (nproc=~6*GIsessions)
 Other Issues

! Rule Number 1: Don’t attempt to run older 5.0 minor versions

of filePro with current GIserver. Be sure to load current
version from www.fptech.com site for best results.
< Minor version numbers have some major changes with
regards to GIserver. Licensing and messaging have
changed to stabilize the GIclient.
! Menu comes up, but can’t move to another menu.
< Character filePro Version doesn’t match GIserver version.
! Since early versions required licensing each GIclient, a new
GIserver license is required when updating from a earlier
version.
 Other Issues

! Larger systems may require increasing the number of record

locks in Unix (FLCKREC) if deadlocks appear.
! Password refuses to login in, but returns to login screen.
< Be sure you still have users counts available.
< In the ~/giserver/users/Username.cfg be sure the password
entry line is followed by a carriage return.
! Variables set in ~/giserver/users/Username.cfg are not
retained.
< Move the variable above the password variable in the
Username.cfg.
 What to send to support?
! Versions of both character and GIserver
! Log from GIclient having the problem.
< ~/fileprogi/fileproGI.##.##.##.##.dat on Client Side
! Logs from GIserver side
< Logfiles consist of:
P scraper.log (PFSCRAPERLOG=/tmp/scraper.log)
P daemon.log (PFDAEMONLOG=/tmp/daemon.log)
P daemon2.log (Unix /tmp folder)
P ~/giserver/logs/user##_##_##_##.dbg (debuglog=true)
P ~/giserver/logs/user##_##_##_##.log
P ~/giserver/logs/giserver.err
P ~/giserver/logs/giserver.log (log=true)
 ~/fp/giserver/users/user.cfg
To Get a Login parameters setup

~/fp/giserver/giserver and for

~/fp/giserver/fpdaemon_sco or
Unix ~/fp/giserver/lserv must be
~/fp/giserver/fpdamon_nt is executed.
running to validate license

~/fp/giserver/lib/giserver.cfg is If variable set

evaluated for location of PFDAEMONLOG=/tmp/user.daemon
executables and port numbers, etc begins logging

If variable set
This is validated against the PFSCRAPERLOG=/tmp/scraper.log
~/fp/giserver/lib/giserver.lic file begins logging all GI-related filepro
programs activity. No logging for
non-filePro programs.
~/fp/giserver/users/default.cfg
parameters are setup

User connection from GIclient Menu Appears from startcmd

 Variables to determine information send to
giserver.log
! logPrograms=true – logs entry (program name, pid, user session name)
and exit of all filePro programs started through GIserver.
P logConnections=true – logs connects and disconnects of all user
sessions also logs any remaining server-side programs (fpdameon,
runmenu, etc.) attributed to that session and attempts to kill those
processes
P logHeartbeat=true – logs all hearbeat ("are you still there")
messages sent to GIclient. Logs failure of GIclient to respond
within expected time frame and logs shutdown of session if three
consecutive messages to that session's GIclient have not been
responded to.
P logAdmin=true – Server response to some GIadmin requests.
P debugraw=true – logs all non-filepro related commands bits