For the last hour I have been struggling with VB6 and a really irritating problem that I think is a bug in their IDE or something.

I'm trying to get AnnaVU saving into the logo editor.

I have a function called "SaveBinFile" that takes one parameter: The path and file name to save.

Looks like this:

Sub SaveBinFile(PathAndFileName As String)

I want to extend this and add another parameter to handle saving AnnaVu files:

Sub SaveBinFile(PathAndFileName As String, Optional AnnaVu As String)

This is all fine. Since the argument is optional, the original calls to this function still work. But when I try to call the function with two parameters, there is a syntax error. The IDE tells me there's a second parameter there just fine in the quickinfo, but it won't let me add it.

Even If I make the second parameter non-optional...

Sub SaveBinFile(PathAndFileName As String, AnnaVu As String)

Same problem. The IDE won't let me enter any call to this function with two parameters. The IDE thinks that one parameter is good, and two parameters is evil. Screen shots:



AAAARGH!!!!

I seem to remember experiencing something similar, I _think_ I got around it by declaring the 2nd argument as type Variant, YMMV.

Try getting rid of the parens when calling it, i.e.
SaveBinFile param1, param2

Looks like a case of VB letting you get away with murder and then having an unhelpful error message.

If you take the parenthesis off the problem will go away. If VB wasn't quite so lax about letting you call Subs with parenthesis then you would never have hit the problem.

Prefixing the call with "Call" will also fix it.

I've struck this problem too. The cause is not obvious, the solution is.

In VB if you put brackets around a variable/parameter, it tells VB to convert the parameter to a string. Using the same syntax to the call a procedure, confuses VB, so it assumes that as its a procedure, it never returns any value, so brackets are not required so you must mean you want to convert the parameter to a string first.
So stating:
myproc(param1)
is different from:
myproc param1
or
call myproc (param1)

What VB is complaining about in your original situation was that you appeared to be trying to concatentate two parameters/variables into a single string.
e.g myproc (param1,param2)
Is seen by VB (wrongly) as (param1,param2) i.e. convert param1 & param2 into a combined string via () then call myproc with one argument.

So, as per Andy's comments, sticking a call in front, or removing the brackets will fix the problem.

The above explanation is why it fixes the problem.

Thanks, all three of you who supplied the information about the parens. I will do that. I'm sure it will work.

I love this BBS.