| DaeHee,
> I want to know how I can use DECforms instead of FMS.
Not in combination with ALL-IN-1.
> And if I can't , when do you suppose can I use DECforms?
Future is discussed in ABBOTT::A1INFO . Last discussion
about DECforms was in november 1990 I think. Not a
hot topic. The official statement is predictable:
"Will or will not be considered to be or not be implemenented
in ........."
Regards,
Jan
|
| The best answer to this, I believe, is to ask how you want to use
DECforms. If you want to substitute it as the default form manager in ALL-IN-1,
you've already got your answer. But that should be apparent by the API of
ALL-IN-1 being driven by a form's Named Data... something that doesn't exist in
DECforms.
Now, on the other hand, if you want to write an application (typically
in a 3GL) that uses DECforms as *its* UI, then there's no problem. You can
certainly integrate DECforms applications in this manner with ALL-IN-1 today.
The disadvantage, of course, is that you have created a second UI, such that
while the user is running that particular portion of their application, they
will certainly be aware of the lack of consistency in such things as Gold-I
interrupts, Gold-H help, and various other user-defined keystrokes. But for
those who *must* have DECforms (something I've never understood -- that is,
the concept of defining the tool before you define the job), it can be done.
F
|
| I wrote a program in Pascal which used DEFforms. The project decision was
that DECFORMS was the technology to use. So, from within ALL-IN-1, I just ran
the program in a command procedure which was called from the named data
(the user selected his report to run from an ALL-IN-1 screen).
Nothing more elegant than that. But I guess you are looking for more of an
inrtegration capability.
There is no ACMS style of passing data to DECFORMS such as
RECEIVE FORM RECORD EMPLOYEE_INFO_RECORD RECEIVING
EMPLOYEE_INFO_WKSP WITH RECEIVE CONTROL QUIT_WORKPACE
-- Dave
|