[RESOLVED] OutputTo not available ACCESS 2010
Hey all,
So at work lately, I've been converting all of our automated databases from a PC over to a virtual server. One big difference and time consuming process for me has been adjustng all vba code to work with 2010. the old pc was still using 2000. :rolleyes:
So, my latest problem seems to be with getting the error OutputTo command is not available. All of these databases are run via task scheduler and either run a macro that then opens a form, or opens the database itself with a startup form getting launched.
I thought I had the issue resolved, by switching from macros to startup forms, as it seemed to resolve the issue for a week. (I think its due to the navigation pane not being visible in 2010) - which I thought was related to a macro opening a form.
I have searched for a few weeks now, and can't seem to find a definite answer to this problem. Hoping someone here has some insight on this, or a possible work around.
docmd.transferspreadsheet works fine, however I need outputto for ths particular database that exports reports and rtf files.
Note: the same database will run fine If i manually open the database and launch the form. No errors get thrown. Only if task scheduler launchs the database via macro ...and apparently now even if a startup form launches with no macro.
Re: OutputTo not available ACCESS 2010
Just an update here; in case anyone else is having this same problem.
I've setup the database to run without any command line switch. this database in particular was using the /runtime switch. So i've taken that off and will see how that goes in the morning when it's scheduled to run again.
Re: OutputTo not available ACCESS 2010
Changing the commandline switch to get rid of /runtime seemed to solve the problem. Still have to make sure the task is opening just the database and not a macro though. Running the form via macro from scheduler still doesnt start the navigation pane it seems and causes issues with OutputTo.
So all solved, for now.