Whoops! Yeah, I pulled out the Subs for ADO_Error and WMI_Error as well as the source for WMIQuery.
The two subs only call a SendMail routine I use to inform me that someone's PC has a problem with running the logon script - they're not hugely informative, its really just flags them up as needing a look at.
Sorry! Obviously WMIQuery is a dependency - but I wouldn't want to post it in case it looks like I'm trying to claim credit for it!
I rolled this out so long ago now I can't remember if there were any other things that I had to do to get it working. I don't "think" so!
In fact, I think that the earlier version of this script was about my only contribution of note to the board - and it followed on from the question "How do I write to an Access DB?"
![[Wink]](images/icons/wink.gif)
How time flies - and how little I've had to offer in between...
I had originally hoped to take my antiquated Access-based Helpdesk DB, convert it to an ASP-based solution and enable it to read from this DB as well to create a more useful tool - you know, someone logs a call with the Helpdesk, and while the 1st liner is taking the details, the ASP is returning data about the users PC, and the user themselves - justs speeds up the gathering of that data by other means. Could put in hyperlinks to the PCs admin shares, etc - lots of stuff that is available in the DB now, just not very easily accessible, or friendly looking.
Shame my boss doesn't want to pay me to sit on my fat a**e and play with code all day...
[ 03. November 2003, 19:42: Message edited by: Breaker ]
_________________________
================================================
Breaker
