FMPro V6.04
Windows XP
----------------------------
I'm not sure where to begin here or if this would be arguable better
done with a newer version of Filemaker Pro...

My users need a way to report how many times different modules are
used in all the different records in multiple databases. Different
databases deal with how issues are worked out, and who generated them
(outside the company, versus internally, versus formallity).

They want to know the number of times each SW MOD is used by project,
and they'd like the option generating a list of workplans and problem
reports that called on any given module for resolution to it's issues.
==========================================
i.e.,

abc.ada is touched by 500 workplans in our workplan database
*(the workplan database has a SW Mod child db that actually holds
all
SW information)

abc.ada is touched by 76 Internal Workplans in our Internal Workplans
database
*(the Internal Workplan database has a SW Mod child db that actually
holds all the SW information)

abc.ada is touched by 200 problem reports in our problem reports
database
*(the Problem Reports database does not have any SW child
databases,
just a field that our engineers have been entering in modules
affected)

Therefore, adc.ada is touched by a total of 776 different records from
all database entries from all databases involved.

================================================== ========
I know that I will need to create a child databases for the Problem
Reports database to contain all the software mod's affected for that
database.

But then, how do I create a report that can pull the total number of
times modules are used?

I'm confused as to how to gather totals from multiple child databases
1) Workplan SW Mods
2) Internal Workplan SW Mods
3) Problem Report SW Mods

The purpose of this report would be to show the most problematic
modules across the board, in addition to the user then wanting to be
able to generate a report telling them what Workplans and Problem
Reports are using a particular SW Module.

This is just a multiple:multiple nightmare that I cannot get my mind
wrapped around and don't know if this is possible with V6.0, or if
going to a new version of Filemaker would make it easier to assertain.

Any help would be greatly appreciated.

Thank you.

- Teresa

Teresa K. <teresa.kabourek (AT) ngc (DOT) com> wrote:

The easiest way to do this seems to me to have every script calling one
of your SW modules create a record in an single log database, with
fields for the date, the calling database, perhaps the calling record,
and the called module. In this log database you may define all sorts of
reports.

--
Hans Rijnbout
Utrecht, Netherlands

Hans,
Just to confirm, this fix would require my making another new database
that would simply act as a repository for records made in my other
databases, and then I could make subsequent scripts from this
repository... interesting... I'll see what I can do. Thanks for the
suggestion.

And for anyone else out there with idea's, please do post. It would
be interesting to see different methods to handle this. Thanks.

- Teresa