>>VB supports named parameters, and VFP does not; you have to make the parameters appear in the correct
>>order, comma-separated, allowing for any internvening non-defined values passed to the method.
>
>So presumably one way to do this would be to create a free table which has a field for each of the parameters (appropriately labelled), then write a little 'composer' which would write the correct syntax into a statement. That way (once you get the composer working right) the thing would be, in essence, like having named parameters and I wouldn't have to worry about dropping a comma or something. does this make any sense?

Yeah Bill, you could do that, but the essence of what we're saying is that you have to pass the parameters in the correct order in VFP as in:
oword.activedocument.printout(.t.,,,,2,.t.) whereas in VB you can pass them in any order you want using the vba constants.