well dude...somebody's gotta do the dirty work! :P

the real world in consulting. never been there so far ;).

ay yeah. I remember the time when I had to ask dehran_ph why I cant what is wrong with my ADO statement here:

cmd.CommandType = adCmdStoredProc        

cmd.Execute("InsertQueryName",Array & _(Parameters))

for freaking out loud Im using an insert query in MS Access and the ADO statement is showing the error "Expected: =". So I would have to modify my statement in to this

cmd.CommandType = adCmdStoredProc        

Set rs = cmd.Execute("InsertQueryName",Array & _(Parameters))

Its sking for a recordset when MS Access dont return recordsets. It turn out that this is the correct syntax

cmd.CommandType = adCmdStoredProc        

cmd.Execute "InsertQueryName",Array(Parameters)

It turned out its those freaking parantheses that's causing the problem

Physics grad ka pala. Ako din eh. :p

But I did tinker with VB6.

sana ako hindi ma-assign sa VB6, he he

Aren't you just missing "Call" before "MsgBox", as it's a procedure?

bah, if you want to call a function or sub with parenthesis and not have to get a return value write:

Call MyFunction(bla, bloum)

it is the same as

MyFunction bla, bloum

but at least you have the parenthesis... I just hate the "Call" word... it puts blue everywhere and makes the code quite confusing sometimes, but I prefer it to calling functions or subs without parentesis.

As someone mentioned, this "call" is not needed anymore in .NET... what a relief...

(like the "Set" for the objects... given that everything is an object, even the in-built types, I found that illogical too...)

Have fun!