using CALL to call methods mandatory?

I've got several classes declared within a module and these classes contain ONLY procedures, no functions.

For some reason when I attempt to run a procedure from the classes, excel screams:

{
Combile error:

Expected: =
}

Seems to me like it thinks one of my procedures is a function? But at the same time, Excel has no problem with the call as long as I use the CALL key word. But whats EVEN MORE STRANGE is that excel excel expects the CALL key word only in front of CERTAIN procedure calls. I can't figure it out! They're all procedures! Some take parameters, some dont, I can't see the logic behind excel's bias!

Are there some sort of special conditions under which CALL is mandatory?

Thanks,

Jerry

The use of ()'s is usually what causes it or not.