By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,969 Members | 2,422 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,969 IT Pros & Developers. It's quick & easy.

Failed to publish report to MS Office Word or Excel

P: n/a
I preview a report and click the button to publish the report to
Word or Excel document. It works correctly until today. It
produced below error message.

Microsoft Office Access can't complete the Output operation.

The Visual Basic code you entered contains a syntax error or the Output
procedures are not available.

Make sure there isn't a syntax error in your code. If the syntax is
correct, run Setup to reinstall Microsoft Office Access. If you want to
preserve your security or custom settings, back up the Microsoft Office
Access workgroup information file.
For information on backing up files, search the Microsoft Windows Help index
for 'backing up files'.

It occurred using toolbar icon or Tools pull-down menu. All the references
are
in place. I uninstalled the Office and reinstalled a clean copy without any
effect. In addition, it did not occur on other pcs.

Any suggestion to the possible causes and fixes are appreciated.

Thanks!

Scott

Dec 2 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Sat, 2 Dec 2006 12:04:29 +0800, "Scott" <No*************@GMail.com>
wrote:

When you reinstall, be sure to install the Full version. You don't
want to leave out the component you so desperately need.

-Tom.

>I preview a report and click the button to publish the report to
Word or Excel document. It works correctly until today. It
produced below error message.

Microsoft Office Access can't complete the Output operation.

The Visual Basic code you entered contains a syntax error or the Output
procedures are not available.

Make sure there isn't a syntax error in your code. If the syntax is
correct, run Setup to reinstall Microsoft Office Access. If you want to
preserve your security or custom settings, back up the Microsoft Office
Access workgroup information file.
For information on backing up files, search the Microsoft Windows Help index
for 'backing up files'.

It occurred using toolbar icon or Tools pull-down menu. All the references
are
in place. I uninstalled the Office and reinstalled a clean copy without any
effect. In addition, it did not occur on other pcs.

Any suggestion to the possible causes and fixes are appreciated.

Thanks!

Scott

Dec 2 '06 #2

P: n/a
Tom,

Thanks for your response. I did reinstall the full version like the first
time when I use this function without problem. It appears to me that the
link to publish report to MS Office Word or Excel is broken or any dll file
is corrupted. Unfortunately, I have no idea about such things and looking
for the advice who has in-depth knowledge about the program.

Scott

"Tom van Stiphout" <no*************@cox.netwrote in message
news:lr********************************@4ax.com...
On Sat, 2 Dec 2006 12:04:29 +0800, "Scott" <No*************@GMail.com>
wrote:

When you reinstall, be sure to install the Full version. You don't
want to leave out the component you so desperately need.

-Tom.

>>I preview a report and click the button to publish the report to
Word or Excel document. It works correctly until today. It
produced below error message.

Microsoft Office Access can't complete the Output operation.

The Visual Basic code you entered contains a syntax error or the Output
procedures are not available.

Make sure there isn't a syntax error in your code. If the syntax is
correct, run Setup to reinstall Microsoft Office Access. If you want to
preserve your security or custom settings, back up the Microsoft Office
Access workgroup information file.
For information on backing up files, search the Microsoft Windows Help
index
for 'backing up files'.

It occurred using toolbar icon or Tools pull-down menu. All the
references
are
in place. I uninstalled the Office and reinstalled a clean copy without
any
effect. In addition, it did not occur on other pcs.

Any suggestion to the possible causes and fixes are appreciated.

Thanks!

Scott


Dec 2 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.