Printers not accessible if UAC is on and Office app is run in elevated mode

Is there any workaround for this problem, in Vista x64, and also in Windows
Server x64 2008 RC1:

With UAC on, if any Office 2007 app is run with admin elevation (Excel and
Access tested), then you cannot print from the app (get error "no printers
defined").

Furthermore, when the apps are set to always run with admin elevation, you
cannot open an office document from Windows explorer ("file not found" even
when double-clicking on it). However, you can run the Office app and then
open the document from within the app.

These seem like fairly major bugs with Vista and/or Office.
Note: I'm running the apps with admin elevation in order that command-line
scripts that are called by VBA also run with admin elevation (and they
require admin elevation).

Thanks.

Is there any workaround for this problem, in Vista x64, and also in Windows
Server x64 2008 RC1:

> With UAC on, if any Office 2007 app is run with admin elevation (Excel and
> Access tested), then you cannot print from the app (get error "no printers
> defined").
>
> Furthermore, when the apps are set to always run with admin elevation, you
> cannot open an office document from Windows explorer ("file not found"
> even when double-clicking on it). However, you can run the Office app and
> then open the document from within the app.
>
> These seem like fairly major bugs with Vista and/or Office.
> Note: I'm running the apps with admin elevation in order that command-line
> scripts that are called by VBA also run with admin elevation (and they
> require admin elevation).
>
Thanks.

Maybe I'm dumb enough to have a smart answer ....upgrade from Vista to XP.



"Tech_vs_Life" wrote:

> Is there any workaround for this problem, in Vista x64, and also in Windows
> Server x64 2008 RC1:
>
> > With UAC on, if any Office 2007 app is run with admin elevation (Excel and
> > Access tested), then you cannot print from the app (get error "no printers
> > defined").
> >
> > Furthermore, when the apps are set to always run with admin elevation, you
> > cannot open an office document from Windows explorer ("file not found"
> > even when double-clicking on it). However, you can run the Office app and
> > then open the document from within the app.
> >
> > These seem like fairly major bugs with Vista and/or Office.
> > Note: I'm running the apps with admin elevation in order that command-line
> > scripts that are called by VBA also run with admin elevation (and they
> > require admin elevation).
> >
> Thanks.
>
>