I am an intern at a major corporation and one of the assignments one of my co-workers decided to direct my way was to make pre-existing VBScript return the neccesary values from an ADSI query.

I am not very familiar with ADSI or LDAP so bear with me if I dont make any sense, and I will try to clarify on any points needed.

This script, when handed to me, worked as is. It got the appropriate values and displayed them in a vbs popup box. Fine.

The problem lied in that the co-worker who assigned this to me could not get it to display 2 extra variables that he wanted included in the query.

The problem appears to lie in the variable type, which is reported as a Long/Interval by the program that he used to display the information locally on the machine.

The query works fine without producing any errors (including the variables in question in the query string is no problem). The problem comes when trying to assign those variables (part of an object) to another variable or trying to display the contents. VBS gives me an error.

I found this odd, so I decided to use the vartype() function to display the types of the variables. The data that was working all returned as the proper type (string, int, what have you). However the data in question, when ran through the vartype() function, reports the variable as type 9 (objects). I found this extremely odd, and I find it safe to say that this is where my problem lies. (of course I cannot assign an object to a normal variable or simply print the object)

Is the query supposed to serve up that variable type as something that would be identificable as an object to VBS? If so, is there a way to convert or process this? Or does this represent some sort of error or problem on the server side, and dosent actually deal with the script at all?

FYI, the variables in question are Long/Interval types that reprsent the data of a users lastlogon date and another data (forget what it corresponds to) that is in the format of a Unix date/time (Unix epoch zeroed).

Thanks for any help you might offer, and I hope my inexperience hasnt butchered the question beyond help. The code in question should be attached to this message as a .vb file. Simply rename the file to .vbs to test or just view in notepad. (.vbs wasnt a valid extension)