procedure parameter question

[peteg]

I have created a procedure called TableFlattening(). When running it
thru a macro, I call this procedure via a function

Public Function DoFlatten()
Call TableFlattening
End Function.

Everything works fine. However, inside the proc I have been using a
hardcoded value for a table name. Now I need it to make it a variable,
and I would like to pass the name of the table to the procedure.

I have changed the signature of the proc to TableFlattening(ATableName
as String).
What I can't figure out is what do I need to do the function that calls
the procedure.

TIA

Pete

[Salad]

pe***@garlic.com wrote:

I have created a procedure called TableFlattening(). When running it
thru a macro, I call this procedure via a function

Public Function DoFlatten()
Call TableFlattening
End Function.

Everything works fine. However, inside the proc I have been using a
hardcoded value for a table name. Now I need it to make it a variable,
and I would like to pass the name of the table to the procedure.

I have changed the signature of the proc to TableFlattening(ATableName
as String).
What I can't figure out is what do I need to do the function that calls
the procedure.

TIA

Pete

Public Function DoFlatten()
Call TableFlattening
End Function.

Public Sub TableFlattening(ATableName as String)
....process code
End Sub

You can pass the table name in DoFlatten
Public Function DoFlatten()
Call TableFlattening "NewTableName"
End Function.

Or pass the name to DoFlatten
Public Function DoFlatten(strTableName As String)
Call TableFlattening strTableName
End Function.

and do something like
=DoFlatten "NewTableName"

I'm not sure why DoFlatten is a function since you aren't returning a value.

[peteg]

The way I understand it, is that if you want to execute a procedure
from a macro, you can not do it directly. What you have to do is call a
function using the RunCode action; the function, in turn, invokes the
procedure you want to run.

Please correct me if this is wrong. I would be more than glad to modify
things. And thank you for your tips; I will test them out, and report
back.

Thanks,

Pete