In Excel 2007, I turned on the macro recorder and printed a sheet to MODI to
get a tif of my worksheet. When I looked at the recorded code I got:

ExecuteExcel4Macro "PRINT(1,,,1,,,,,,,,2,,,TRUE,,FALSE)"

Which is fine as long as it works, but I found it strange to get an old XL4
macro from 2007..........bug?

MS defines a bug as something that doesn't work as designed. I'm sure this
code is produced because MS designed it that way.

Back when VBA was introduced (Excel 5) it could not support every operation
that Excel 4 macros could. And it still can't. Thus the ExecuteExcel4Macro
method. Whether Excel 2007 VBA can do what you recorded or not I imagine MS
didn't allocate resources to revisit what the macro recorder produces, as
long as it works. If Excel 4 macro support is removed in Excel 14, as is
rumored, it probably will (I pray).

--
Jim
"XP" wrote in message
...
| In Excel 2007, I turned on the macro recorder and printed a sheet to MODI
to
| get a tif of my worksheet. When I looked at the recorded code I got:
|
| ExecuteExcel4Macro "PRINT(1,,,1,,,,,,,,2,,,TRUE,,FALSE)"
|
| Which is fine as long as it works, but I found it strange to get an old
XL4
| macro from 2007..........bug?
|
|