M
Maury Markowitz
I'm trying to use Access as a way to run an automated report every
night. Excel doesn't have a command line switch for this, so I wrote a
little stub in Access that opens Excel and calls the macro (I have
literally hundreds of similar examples).
If I run the macro by hand it works fine. But when I call it from the
command line Access says that the macro cannot be found. Yes, it IS
spelled correctly. Any ideas?
Another problem is that if Access is already open when the command
line runs, an error about it being in read only mode appears. That
"freezes" everything until I click the Ok button. Is there some way to
avoid this? I tried the /ro flag, but that just makes the dialog
appear EVERY time (thanks MS).
Maury
night. Excel doesn't have a command line switch for this, so I wrote a
little stub in Access that opens Excel and calls the macro (I have
literally hundreds of similar examples).
If I run the macro by hand it works fine. But when I call it from the
command line Access says that the macro cannot be found. Yes, it IS
spelled correctly. Any ideas?
Another problem is that if Access is already open when the command
line runs, an error about it being in read only mode appears. That
"freezes" everything until I click the Ok button. Is there some way to
avoid this? I tried the /ro flag, but that just makes the dialog
appear EVERY time (thanks MS).
Maury