[AccessD] VBA code to acquire system stats

ROTFL.  The poor people get suckered, and then you rub it in. 


John W. Colby
Colby Consulting
www.ColbyConsulting.com 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Tuesday, January 15, 2008 12:44 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VBA code to acquire system stats

I sent something to you and JWC, but it bounced back from JWC.

http://www.marlow.com/ISFE2007Service.zip

It's the source to a VB based NT Service that I wrote (minus one class, to
connect to the database, sorry, it has passwords in it).  I'll leave that up
for a few days.  It's got lot's of classes that I wrote to get all sorts of
system information.  There is some custom error handling (to deal with being
an NT Service), other then removing/modifying that error handling code,
these classes are pretty much stand alone.

The CPU one does use a .dll (which is in the zip), in a last ditch effort to
get CPU information.  If I remember correctly, it only uses that for Windows
95, everything else can use WMI or registry reads.

One class I think some people might like is the OperatingSystem Class.

Ie:

Dim os AS OperatingSystem
Set os=New OperatingSystem
If os.WindowsVista then MsgBox "I'm sorry, you've been suckered into using
an OS that Microsoft should have never released!"
Set os=nothing

<grin>

Yes, that code would work too.  It has strings properties for OS Type,
Version, Build, ServicePack and Name.  It also has Boolean properties for NT
Based, NT4, Windows 2000, XP, 2003, Vista, Server, and DomainController.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Bartow
Sent: Tuesday, January 15, 2008 11:13 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] VBA code to acquire system stats

It was an attachment so I couldn't post it here. I just pulled it all out of
humongous library and sent it off. There's a lot of extra weight in it that
isn't needed but that be cleaned up too. My Library is all categorized
modules containing a group of somewhat related procedures. When I pull code
from other people that replicates what something in my library already does
it gets cleaned up and any similarities are replaced with what is already
there. 

For example:


--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com