"Sofware Applications" inventory system. 2

[bsupport]

Does anyone know of a Microsoft Access "Software Inventory" database application? I have searched the internet several times and can not find anything such as this.

I am using Access 2000 to design a database where I can track all of the software that my organization purchases, stocks, installs , returns, and discards (life cycle of a software medium within our organization) and would like some examples to look at.

Does anyone have any info!

Your response is greatly appreciated.

 

[LarryDeLaruelle]

One of the built-in databases templates provided with Access is an Inventory System.

Start the Access application and select Database Wizard. On the next screen select Inventory Control.mdz.

Access will then lead you through several steps to create a complete database for inventory.

This should give you a good sample to review and a place to start developing your own system. It's even possible that you can create the guts of what you need from this.

Good luck.
Larry De Laruelle
larry1de@yahoo.com

 

[bsupport]

Thanks Larry , but....

This was the first place I looked :-(. It is too "inventory" oriented and not enough "where has this software been", "where is it now", or "when did we get rid of it" oriented.

I'm not interested |-I in things like how much it cost, what was the purchase order number, or who was the supplier/shipper. Those things are handled in another system that will not be modified for many years. What I need is more of a daily tracking mechanism i.e., WHAT computer was WHAT software was INSTALLED on/REMOVED from/UPGRADED to/DISCARDED when, and on WHAT day and by WHOM.

Thanks for your response anyway though, I appreciated it ;-).

 

[LarryDeLaruelle]

bsupport:

Sorry my post wasn't more helpful I didn't mean to indicate that what MS provided would be a one size fits all solution. Only that by looking at what was provided you might get some ideas for designing your own.

From your description, it sounds like you need a db with three tables: Main table of Systems, Secondary table of Transactions (installs/uninstalls/upgrades) and a lookup table of software titles. Is this getting the the core of your question?

The main table would contain all information necessary to describe the system and, perhaps, use the seriel number for the primary key.

The secondary table would contain the system's primary key, transaction date, software title (code only-link to the lookup) and other info on who, what, etc.

The look-up table would only contain information specific to the software titles (name, version, etc) and a record number. The seriel number may be a good choice if you want to track specific licenses or an autonumber field if you only need a linking field.

Hope this gives you a bit more of a starting point. Let me know.
Larry De Laruelle
larry1de@yahoo.com

 

[bsupport]

THANKS Larry!

Yes, this is more of what I need.

No, I'm sorry I was not more specific (what do they say about hindsight?) Anyway, thanks again for your help and suggestions. You've pointed me in a direction that links to a rode going somewhere now.

Have a great rest-of-the-day *:->* Who takes 7 seconds to develop,
7 mins to document,
7 hours to test,
7 months to fix will always blame the clock. s-)

 

[LarryDeLaruelle]

bsupport:

You have hit the nail on the head. I usually invest a significant number of hours with paper and pencil as a first step in developing a new database before I ever touch the keyboard.

I've yet to find that it was time wasted.

Good luck with your project.
Larry De Laruelle
larry1de@yahoo.com