Documentation for command parameters for Excel4 calls

[JoeLiuzzo]

The xlcall32.h header file has a long list of function codes <xlfn> starting
from xlcBeep (0 | xlcommand). I understand these are the 1st parameters in a
call to Excel4/4v or Excel 12/12v, but I cannot find any examples or
documentation explaining the variation for the remaining parameters for each
of these commands.

I know the general format s/b Excel4(<xlfn>, result, count, <args>), but I
would think each command has certain required and optional parms. Where can
I find this information?

thanks
Joe

 

[Joel]

YOu can open excel and search the help. Try this search page in excel help

List of worksheet functions (by category)

 

[Michael]

It is becoming more difficult to get hold of the Microsoft Excel 4 Function
Reference. However almost all of the necessary documentation can still be
found in MSDN. Search MSDN using the search string below to find it. (Make
sure you retain the quotes.)

"Converting C-API Add-Ins to 32-bit Microsoft Excel"

 

[JoeLiuzzo]

Thanks for responding, Michael. Perhaps I didn't phrase my question clearly
enough, b/c I've already seen that article but I don't think what I'm looking
for is there. To be more specific, the parameters to the xlcPasteSpecial
command (expressed as XLOPERS) must be quite different than the parameters to
the xlcOpen command. So if I want to open a document using c++ xll code, i'd
have to code something like
Excel4v(xlcOpen, operRes, <count>, <openparms>) and then if I'm using paste
special,
Excel4v(xlcPasteSpecial, operRes, <count>, <pasteparms>)

The number and type(s) of the parameters passed for the open command must be
different than the number and type(s) passed for the paste command, but I do
not see where this is explained in the article to which you directed me.

 

[JoeLiuzzo]

OK, now I think I get it, or "I see", said the blind man.

The number and type of parms are equivalent to what the EXCEL 4.0 macro
language parameters would be.

It took a lot of digging and some trial & error for me to come to this
realization, but it certainly isn't clear from the microsoft documentation!