NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/database/sybase/356

Text File | 1992-11-18 | 1.8 KB | 39 lines

Newsgroups: comp.databases.sybase
Path: sparky!uunet!st-andy!larry
From: [e-mail] (Larry Martell)
Subject: APT rules question
Message-ID: <[e-mail]>
Organization: RMJ Securities Corp.
Date: Wed, 18 Nov 1992 17:51:49 GMT
Lines: 29

In APT you can attach rules to fields on your form. When you compile your
rules, APT pulls the rule down from the server, creates a file with the
rule source in it (with a name of the form RLnnnnform_name.fpl, where nnnn
is the number of the field with the rule attached to it), and compiles that
.fpl into a .fpo.

Now, while this may be fine for a developer working on one form in their own
directory, it is a major problem in an environment where only project managers
have access to production directories. The manager must bring up every form in
APT, compile the rules, and write the form (because compiling the rules creates
a timestamp in the .frm, and it you don't write the form with the new timestamp
the compiled rule will not be executed). This must be done manually. (It is also
a problem if you use SCCS to maintain your forms. After the form has been
checked in, its modes are 444, and your can't save the form.)

Has anyone come up with a method for automating this process? I was thinking
along two potential avenues. The first is to programmatically tell APT to do
its thing (I don't know it this is possible). The second would be a program that
looked into the frm to find out the fields that have rules attached to them,
and then use dblib calls to get the rules from the server, compile them into
the appropriate named fpo, and updates the timestamp in the frm.

Any help in this area will be greatly appreciated.

TIA
--
Larry Martell                  "Opinions are like assholes; everybody has one,
212-668-9478                but nobody wants to look at the other guys"
uunet!st-andy!larry