-
Using TCP ports other than the default of 1412
will work for all server programs.
In order to do so you need to specify the port in
both the _4CSRVRCONFIG file and the XLCONFIG file.
In the _4CSRVRCONFIG file you need a line simlar to:
Connect Type=Socket,Port=1414
In the XLCONFIG file you need a line similar to:
FCPort 1414
If the FCPort line does not exist in the XLCONFIG file,
then compiling programs and running reports will fail.
-
You can have default titles per application for
the sys.get_answer() DialogBox, the Error message
MessageBox, and the Info message MessageBox.
Add lines to the _4CSRVRCONFIG file in the application
area similar to the following:
ErrorWinTitle="4C Error"
InfoWinTitle="4C Info"
GetAnswerWinTitle="4C Input"
-
There is a new system PCL,
sys.message()
that is meant to replace both sys.msg() and sys.err_msg().
-
4c will not allow you to press a cmdbtn unless the
4csrvr is ready for input.
Too many users are double clicking on buttons and causing problems
in the application.
This was especially a problem where the command button executed
a shell command and could cause core dumps.
-
Native database support is available for some databases on
some systems.
-
The 4c windows client will popup a dialog box
when the user presses <CTL><ALT><F8>.
This dialog box will allow you to see
some current connection information and it will
allow you to enter the 4c debugger, exit the
current 4c program, end the 4c session and
to change the NoErrWait option.
-
There is a new 4c srvr program called 4cchecksum.
It can be used with a client program xlcsum to
help verify if a network connection is accurate
or not.
The easiest way to run it is as follows:
xlcsum -c <connect string>
where <connect string> is a normal 4c connection string
similar to the following:
192.168.4.22
or
Machine=192.168.4.22,Type=TCP,Port=1414
Just typing in xlcsum will give you a list of
options.
This program can be used to help indicate if
problems exist on the network but it wont
be able to tell you what to do to fix them.
-
There have been several bugs fixed that caused
the 4csrvr to hang when sys.get_answer() was
called and the user switched to another program
without answering.
-
4C can be configured to force
sys.get_answer()
to use a DialogBox or to use a Text line at the
bottom of the layout.
This is done by adding one of the following lines
to the _4CSRVRCONFIG file.
GetAnswerType Dialog
GetAnswerType Text
These can be overriden per application by one of the
following lines in the application section.
GetAnswerType=Dialog
GetAnswerType=Text
Each client can also override this with their preferences
menu.
Experiment with it and you will see how it works.
-
One last sys.get_answer() item.
sys.get_answer() will let you force either Text or Dialog
box no matter what the server or client settings are by
specifying GA_TEXT or GA_DIALOG as one of the flags.
-
MD5 passwords will work as long as PAM is configured
for 4csrvrd and the _4CSRVRCONFIG file has a line
like:
LogonSecurity PAM
See
Unix Install Notes
for details.