Registrations to Open-AudIT forums are now closed. To ask any new questions please visit Opmantek Community Questions.

Open-AudIT

What's on your network?
It is currently Fri Mar 29, 2024 3:28 pm

All times are UTC + 10 hours




Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 
Author Message
PostPosted: Wed May 19, 2010 11:05 pm 
Offline
Newbie

Joined: Wed May 19, 2010 10:35 pm
Posts: 1
One feature I really miss is having the ability to link one license to multiple software items. This is something we encounter with software with support contracts which include software upgrades. Because the software version is in the software title, every version is a new software item. If not all users use the same software version, it makes it very hard to get a good overview in the Software register.

An example:

Let's say we have 20 Microsoft Open License licenses for Windows 7. These licenses also allow us to run XP or Vista. Let's say 15 users are running Windows 7, but 5 users are running XP. Now I would have to split the license into two with 15 licenses listed at Windows 7 and 5 licenses listed at XP. Now 2 more users are upgraded to Windows 7. Now I have to manually correct the amount of licenses at XP and Windows 7.

Would it be an idea to seperate the licenses from the software items in a separate database table so that they could be linked in a 1 to many relationship?


Top
 Profile  
Reply with quote  
PostPosted: Thu Jun 17, 2010 8:07 pm 
Offline
Site Admin
User avatar

Joined: Mon Jun 07, 2004 11:48 am
Posts: 1964
Location: Brisbane, Australia
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.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 2 posts ] 

All times are UTC + 10 hours


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group