D
Dmitri Karpov
Has anyone else run into this (and found a reason/fix)?
On one of our five test dev machines, Word 2007 has a weird bug.
Start a blank new doc, go into the VBA macro editing area, add the
line:
options.printbackground=false
(on our machine, you can use ANY of the print options for this test -
printcomments, printbackgrounds, printdraft, etc.). they ALL fail...
but the non-print options are fine.)
If I try to run the macro, it breaks on that line with a runtime 4120
error bad parameter.
I've changed it to options.printbackground=true - still no go.
I've tried changing the default printer and restarting word. Still no
go.
Curiously, I can do a:
msgbox options.printbackground
and it will accurately read the value of the printbackground hckecbox
from the word options, advanced, printing section.
so... on this ONE machine, I can READ but not SET the options for
printing programmatically.
Any ideas??? Corrupt install??? Read only xml ini file or some other
obscure weirdness????
Regards.
On one of our five test dev machines, Word 2007 has a weird bug.
Start a blank new doc, go into the VBA macro editing area, add the
line:
options.printbackground=false
(on our machine, you can use ANY of the print options for this test -
printcomments, printbackgrounds, printdraft, etc.). they ALL fail...
but the non-print options are fine.)
If I try to run the macro, it breaks on that line with a runtime 4120
error bad parameter.
I've changed it to options.printbackground=true - still no go.
I've tried changing the default printer and restarting word. Still no
go.
Curiously, I can do a:
msgbox options.printbackground
and it will accurately read the value of the printbackground hckecbox
from the word options, advanced, printing section.
so... on this ONE machine, I can READ but not SET the options for
printing programmatically.
Any ideas??? Corrupt install??? Read only xml ini file or some other
obscure weirdness????
Regards.