From: Fred on
All of the given answer are good.

If you want help going the "make an Access DB" route, then start doing what
the first 3 respondents have said and, if you need/ could use help, repost,
telling us your answers are to the question posed in those responses.


From: freddy on
The problem is that the company does not want to spend money.

"jacksonmacd" wrote:

> I know this is an Access newsgroup, and you are looking for an Access
> answer, but have you considered that you might be reinventing the
> wheel? Perhaps an off-the-shelf solution like Spiceworks
> (spiceworks.com) might save you a lot of work.
>
> But then again, you might be looking to improve your Access skills.
>
> PS. I have no affiliation with Spiceworks or any other similar
> software.
>
>
> On Tue, 1 Dec 2009 07:48:01 -0800, freddy
> <freddy(a)discussions.microsoft.com> wrote:
>
> >I am a desktop support person and I have a vbscript to inventory all the
> >computers on the network. I use the script to gather information like
> >username, memory, hard drive space, and I am thinking about getting installed
> >software. I have the script writing to an excel file, which is ok for now. I
> >would like to use Access 2003 but my problem is the design. Do I create one
> >table and have a field for username, computer name, memory, and so on or do I
> >create more than one table like for username and one for computername. Plus
> >how do I handle the installed software?
> >My idea was to have three tables: one for username which will have full
> >name, one for computername which will have all the computer stuff like
> >memory, hd, etc and one for software which will have software name, version,
> >installed date, etc. Please someone help me out.
> >
> >Thanks
> >Freddt
>
> --
> jackmacMACd0onald(a)telus.net
> remove uppercase and number for true email
> .
>
From: Jeff Boyce on
Oho! Willing to spend people's time/salary, but not willing to purchase
software or hire expertise...?

Best of luck!

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"freddy" <freddy(a)discussions.microsoft.com> wrote in message
news:445B0CFA-A04E-4E19-9105-F4237A81F4A8(a)microsoft.com...
> The problem is that the company does not want to spend money.
>
> "jacksonmacd" wrote:
>
>> I know this is an Access newsgroup, and you are looking for an Access
>> answer, but have you considered that you might be reinventing the
>> wheel? Perhaps an off-the-shelf solution like Spiceworks
>> (spiceworks.com) might save you a lot of work.
>>
>> But then again, you might be looking to improve your Access skills.
>>
>> PS. I have no affiliation with Spiceworks or any other similar
>> software.
>>
>>
>> On Tue, 1 Dec 2009 07:48:01 -0800, freddy
>> <freddy(a)discussions.microsoft.com> wrote:
>>
>> >I am a desktop support person and I have a vbscript to inventory all the
>> >computers on the network. I use the script to gather information like
>> >username, memory, hard drive space, and I am thinking about getting
>> >installed
>> >software. I have the script writing to an excel file, which is ok for
>> >now. I
>> >would like to use Access 2003 but my problem is the design. Do I create
>> >one
>> >table and have a field for username, computer name, memory, and so on or
>> >do I
>> >create more than one table like for username and one for computername.
>> >Plus
>> >how do I handle the installed software?
>> >My idea was to have three tables: one for username which will have full
>> >name, one for computername which will have all the computer stuff like
>> >memory, hd, etc and one for software which will have software name,
>> >version,
>> >installed date, etc. Please someone help me out.
>> >
>> >Thanks
>> >Freddt
>>
>> --
>> jackmacMACd0onald(a)telus.net
>> remove uppercase and number for true email
>> .
>>


From: Jeff Boyce on
Why?

If you already have the data going into Excel, what is it that you expect
Access will do that Excel isn't doing?

Regards

Jeff Boyce
Microsoft Access MVP

--
Disclaimer: This author may have received products and services mentioned
in this post. Mention and/or description of a product or service herein
does not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"freddy" <freddy(a)discussions.microsoft.com> wrote in message
news:C937C8A6-45C1-4224-915B-45060BE6B795(a)microsoft.com...
>I am a desktop support person and I have a vbscript to inventory all the
> computers on the network. I use the script to gather information like
> username, memory, hard drive space, and I am thinking about getting
> installed
> software. I have the script writing to an excel file, which is ok for now.
> I
> would like to use Access 2003 but my problem is the design. Do I create
> one
> table and have a field for username, computer name, memory, and so on or
> do I
> create more than one table like for username and one for computername.
> Plus
> how do I handle the installed software?
> My idea was to have three tables: one for username which will have full
> name, one for computername which will have all the computer stuff like
> memory, hd, etc and one for software which will have software name,
> version,
> installed date, etc. Please someone help me out.
>
> Thanks
> Freddt


From: PieterLinden via AccessMonster.com on
freddy wrote:
>The problem is that the company does not want to spend money.
>
>> I know this is an Access newsgroup, and you are looking for an Access
>> answer, but have you considered that you might be reinventing the
>[quoted text clipped - 26 lines]
>> remove uppercase and number for true email
>> .

In that case, you could do an estimate of how much time it will take you to
write something that does close to what they want and come up with a cost to
have you do it. If buying something is cheaper than having you do it, they
may go that route. if they don't bite, then you may be forced to DIY. The
upside is that you learn, the downside (obviously) is that it takes time to
learn and some trial an error...

--
Message posted via http://www.accessmonster.com