Yep - it's a design fault in Open-AudIT. OAv2 will do this as below...
software table system_id software_id software_title software_version
software match table match_id common name select_software
software and software_match software_id match_id
license table license_id match_id number_purchased date_purchased etc etc
So, you have the software table that lists all software and links it to the relevant system.
We create another table that identifies a particular piece of software and gives it a "common name". Included in this table is the required SQL to match the title(s) from the software table.
We have a third table that lists the id matches between the first two tables.
We have a forth table that lists actual purchases. Date, number purchased, etc, etc. It links to the second table to find matches in the first table.
Oh, forgot - we also need to account for Groups in there too !!!
Not to worry - I have it all worked out, I just need the time to implement the whole damn thing in OAv2...
_________________ Support and Development hours available from [url=https://opmantek.com]Opmantek[/url]. Please consider a purchase to help make Open-AudIT better for everyone.
|