[comp.databases] Is anyone using FOURGEN's CASE tools?

dlu@wobble.uucp (Doug Urner) (05/24/91)

And if you are would you care to comment on them?  Specific things I
would like to know are:

	How much trouble is it to maintain code across releases of the
	tools (and the accounting modules if you are using them)?

	Do you have the option of using vi or emacs (as opposed to the
	editor built into the screen generator)?

	Is it possible to modify the behavior of the "User Control Library"?
	Does it really make it possible to control users :-?

	How is FOURGEN's technical support?

Other comments are welcome too.

Thanks, Doug
-- 
Doug Urner, dlu@wobble   "They tear down our comrades like leaves from a tree,
dlu UNIX Consulting       leaves from a tree, leaves from a tree, but the
Bellingham, WA            tree still stands, its roots locked to the land."
206/676-5759                              -- Song of the Exile,  Barry Guilder

larry@cs.widener.edu (Larry Sigmond) (05/25/91)

In article <1991May24.164919.13572@wobble.uucp> dlu@wobble.uucp (Doug Urner) writes:
>	How much trouble is it to maintain code across releases of the
>	tools (and the accounting modules if you are using them)?
>
Releases of the tools and the accounting modules have been reasonably
upward compatible.  Beginning with the current versions future
accounting releases will apply even to _user modified_ code.  The
current version of the screen generator allows you to put code
fragments (including function calls) into a "triggers" file after
special keywords (before_field<name>, after_input, on_disk_read, etc.
-- there are dozens).  Upon code generation these sections are
inserted into the appropriate places in the generated functions. Thus
you can modify the screen and have your custom routines added at
each regeneration.  In particular, you can apply your triggers file
to a later version of an accounting program and so have your
custom work upgraded.

>	Do you have the option of using vi or emacs (as opposed to the
>	editor built into the screen generator)?
>
Yes, you can use vi or emacs with the screen generator, but I
suspect you are thinking about the painter, which really isn't
an editor.  The painter produces text files which are input to the
code generator.  You can use any editor to create or modify these
text files (and, in fact, you don't need to use the painter at all).
You can also go pack and forth (with care) between the painter and
an editor.

>	Is it possible to modify the behavior of the "User Control Library"?
>	Does it really make it possible to control users :-?
>
Neither -- sorry.

>	How is FOURGEN's technical support?
>
Their telephone support, technical customer updates, and their new
"Tool Notes" are all very good.  I look forward to more exchange
here among the user community.
--
Laurence Sigmond    Logical Systems   215-848-8889   larry@logsys.com