Consultor Eletrônico

Actuate vs. Progress international settings

INTRODUCTION: (also read the bottom to implement this in Proctrl)
=============
There is a Kbase # 17073 that explains how to setup an additional
.pf for the OIB executable to avoid the -E and -d params for Actuate
That one is written for UNIX only.
This one takes care of the NT solution

WHY YOU NEED TO KNOW THIS:
===========================
Actuate can't read Progress international parameters like -E and -d
Actuate rely on the O/S settings when printing the result of a field.
If you need to run both Progress clients and Actuate client with
international settings, this is the way to do it.

PROCEDURAL APPROACH:
====================
In your startup.pf which resides in your DLC directory, you keep your
international parameters.
Copy the startup.pf to a startup-oib.pf and remove thoose settings in
that file.
Make a .cmd file like:
SET DLC=C:\DLC
SET PATH=%PATH%;%DLC%;%DLC%\bin
SET PROOIBRK=%DLC%\bin\oibrkr32.exe
SET PROOIDRV=%DLC%\bin\oidrvr32.exe
SET PROSTARTUP=%DLC%\startup-oib.pf
REM To allow OID to access the database via SHM move to DB directory
cd c:\working-dir
%DLC%\bin\oibrkr32.exe -SV -S act-serv -H localhost -N tcp
exit

Use this .cmd file to start your OIB enviroment and then you can set
any "view" format in Regional Settings on your O/S.

Happy Actuating, JBE 22'd january 1999

After this was written, I made some extensive testing together with
jah and we found a way of implementing this in Proctrl.

Make a new entry under "OtherTasks" in Proctrl.
Call the cmd.exe in "Executable Name" like c:\winnt\system32\cmd
Set the working dir (same as database dir)
Call the Oib.cmd (the file explained above) from "Startup Parameters":
/c start <path>\Oib.cmd

Now you can mark the Autostart box and if you have the same on
your database in Proctrl you only need to start ProSrvc (Start on
Proctrl) to start your entire setup.

JBE 2'd february 1999