vbs to autoit for AD

[arcker]

hello evry1; i'm in trouble with objects ! i've read the help file but it's not enough for my problem.

So, i want to use autoit to create an UO under active directory. I've the code for the vbscript, but i want to

translate it, so, here is the code in vbs :

txtOUracine = "LDAP://OU=" & txtConteneur & ",DC=Vaio,DC=dom"
Set objOU = GetObject(txtOUracine)

if err.Number<>0 Then
  WScript.Echo "Error : UO base non found" 
else
txtMonOU="OU=" & txtNomOU
  Set objMonOU = objOU.Create("organizationalUnit", txtMonOU)

and here my translate

$txtOUracine = "LDAP://OU=" & $txtConteneur & ",DC=Vaio,DC=dom"
$objOU = Objget($txtOUracine)

if @error<>0 Then
  msgbox(0, "Erreur : UO base non found" )
else
   $txtMonOU="OU=" & $txtNomOU
 $objMonOU = objcreate("$objOU.organizationalUnit", $txtMonOU <=the problem !

so, i'm good ?

thx again

have a good day

[DaleHohm]

$txtOUracine = "LDAP://OU=" & $txtConteneur & ",DC=Vaio,DC=dom"
$objOU = Objget($txtOUracine)

if @error<>0 Then
  msgbox(0, "Erreur : UO base non found" )
else
   $txtMonOU="OU=" & $txtNomOU
 $objMonOU = objcreate("$objOU.organizationalUnit", $txtMonOU <=the problem !

You'll probably need to check isObj($objOU) instead of @error -- this behaviour is different than vbs:

$txtOUracine = "LDAP://OU=" & $txtConteneur & ",DC=Vaio,DC=dom"
$objOU = Objget($txtOUracine)

if not isObj($objOU) Then
  msgbox(0, "Erreur : UO base non found" )
else
   $txtMonOU="OU=" & $txtNomOU
 $objMonOU = objcreate("$objOU.organizationalUnit", $txtMonOU <=the problem !

Dale

[arcker]

thx for the error solution ! but for the last line of the code, is it correct ?

because to confirm the add, in vbs there is :

objMonOU.SetInfo

how translate it in autoit ?

[jefhal]

objMonOU.SetInfo

how translate it in autoit ?

I'm not aware if AutoIT does this natively, but I'm using Admod/Adfind from www.joeware.com to modify existing objects. Unfortunately it cannot add new objects. Edited October 30, 2005 by jefhal

[DaleHohm]

Ohhh... OK.

I must say that you camouflaged your question in the code block of the base post quite expertly

Assuming that the code works in vbs, the last line should not be translated into ObjCreate in AutoIt. Instead, it appears that the objOU has a method of "Create", so it would be translated to

$objMonOU = $objOU.Create("organizationalUnit", $txtMonOU)

I'm not sure I understand the question about objMonOU.SetInfo -- it should simply translate as $objMonOU.SetInfo or you could do

$result = $objMonOU.SetInfo

Did I understand your questions?

Dale

[arcker]

yes you have understand and thanx for the answer

browsing the forum i've found a post that say there is test of com objects in the zip of beta version, but i can't find them

it would be useful

thx for the solution, because i didn't now that autoit is able to do "*.setinfo" and other

i can't test my script for now, but it seems there is no error, so when i'll test it, i'll inform you

thx again dale, you're amazing !