HELP (Richard Kreiss)

[Tom Aldridge]

Perhaps an idea that might be useful to you.

I run nearly all output processes (printed output as well as maintenance 
processing) from a filePro file itself.

I call the file 'cron' (I know... a dumb name) but I chose it years ago 
because in addition to running a particular output process on demand via 
input processing while sitting on a particular record; I have "cron" 
[the unix/linux utility)] run the following nightly "/appl/fp/rreport 
cron -f cronrun -v cronsel -a -u -ia -bs -bg > /dev/null)"

in order to select records based on fields in 'cron' that duplicate many 
of the features of "cron" itself, i.e. every day, day of week, etc. plus 
criteria such as run one time and delete it's own record, run every so 
many days and increment a set number of days, etc. So when I have a new 
output process to run unattended, I don't have to create a new entry in 
crontab, I simply add a record to my 'cron' database... and there I tell 
it when and how to run.

The 'cron' database contains all sorts of records for running various 
printed reports or maintenance processing, i.e, archive/purge/update 
records.... on other filePro files.

It has fields like:
8 -   a1) fp_command_line                     .    66.  *
9 -   a1) fp_command_line                     .    66.  *
10 -   a1) fp_command_line                     .    66.  *

that I string together (and run via "system") in input processing to run 
on demand, as well as in report processing, see "cronrun" above.

There are other fields that name the report, describe it in detail if 
desired; fields that specify printers, email addresses to send results 
to, etc.

This being a filePro file itself, one can create as sophisticated a user 
interface and search mechanism as desired. No menus to hunt through, 
just a filePro file to select records (i.e. reports) from. For various 
divisions or departments, you can use qualifiers as well.

I know everyone has their own way to do things. This system works great 
for me. Below is part of the map for this 'cron' file.

job_name: 35:allup:
type: 11:allup:
a0)description: 35:*:
a0)description: 35:*:
user_access:  1:yesno:
.:::
run_fp:  1:yesno:
a1) fp_command_line: 66:*:
a1) fp_command_line: 66:*:
a1) fp_command_line: 66:*:
run_shell_command:  1:yesno:
a2) command_line: 66:*:
a2) command_line: 66:*:
a2) command_line: 66:*:
.:::
---individual notification fields---
email_notify:  1:yesno:
email_address: 25:*:
subject: 25:*:
a3) message: 66:*:
a3) message: 66:*:
run_cron:  1:yesno:
dow_numeric:  1:.0:
dow_alpha:  3:allup:
day_of_month:  2:.0:
month_of_year:  2:.0:
run_once:  1:yesno:
run_delete:  1:yesno:
run_mult:  2:.0:
run_on_date: 10:mdyy/:
a3) message: 66:*:
increment_days (to run_on_date):  3:.0:
delete_on_date: 10:mdyy/:
run_days_past_moend:  2:.0:
~

Tom Aldridge



>
> On 4/8/2011 4:37 PM, John Kerr wrote:
>> I am having trouble keeping track of everything having to do with filepro.
>> I am trying to find a solution to organize/manage reports, selections,
>> user menus so we can determine what does what.
>> I have some 300 user menus, some 3000 reports and selections, etc.  I am
>> losing control of information for my people.  I
>> am sure I can develope something but would rather find someone that has
>> already solved the problem.  I can forsee that it would take me a year
>> or more
>> to develope something myself that works.  Need some HELP.
>>
>> johnkerr at combotronicsinc.com
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>