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

Windows XP Will Not Allow Output To Action

P: n/a
Perhaps someone has experienced this problem. I developed an Access 97
Runtime database on a Windows 98 SE machine. I have three reports that
can be optionally copied to a floppy disk or hard drive through use of
a macro: Output To, Report, the name of the Report, Rich Text Format,
Output location and file name, and Auto Start - No.

The process has worked flawlessly when running the macro on Windows 98
SE under Access 97 SR2b on the host machine as a .mdb and also after
being compiled as a .mde and also in Runtime. Additionally, the macro
has run successfully on another Windows 98 SE machine in Runtime with
no Access program installed.

However, after installing the Runtime version on a Windows XP machine
the macro action, for all 3 reports, failed. Why would this happen? I
have decided to change the process from a macro to VBA code instead.
Other than doing this, I don't know of any other options to pursue.

Your assistance in this matter will be appreciated. Thanks, Dalan
Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
On 4 Jan 2004 22:36:42 -0800, ot***@safe-mail.net (Dalan) wrote:
Perhaps someone has experienced this problem. I developed an Access 97
Runtime database on a Windows 98 SE machine. I have three reports that
can be optionally copied to a floppy disk or hard drive through use of
a macro: Output To, Report, the name of the Report, Rich Text Format,
Output location and file name, and Auto Start - No.

The process has worked flawlessly when running the macro on Windows 98
SE under Access 97 SR2b on the host machine as a .mdb and also after
being compiled as a .mde and also in Runtime. Additionally, the macro
has run successfully on another Windows 98 SE machine in Runtime with
no Access program installed.

However, after installing the Runtime version on a Windows XP machine
the macro action, for all 3 reports, failed. Why would this happen? I
have decided to change the process from a macro to VBA code instead.
Other than doing this, I don't know of any other options to pursue.

Your assistance in this matter will be appreciated. Thanks, Dalan


Are you sure the problem is Windows XP per se, or is the problem that there is
no default printer?

When you try to print, preview, or export a report, it normally tries to
format for the default printer on the machine and fails with an error if there
isn't one.
Nov 12 '05 #2

P: n/a
Steve Jorgensen <no****@nospam.nospam> wrote in message news:<k3********************************@4ax.com>. ..
On 4 Jan 2004 22:36:42 -0800, ot***@safe-mail.net (Dalan) wrote:
Perhaps someone has experienced this problem. I developed an Access 97
Runtime database on a Windows 98 SE machine. I have three reports that
can be optionally copied to a floppy disk or hard drive through use of
a macro: Output To, Report, the name of the Report, Rich Text Format,
Output location and file name, and Auto Start - No.

The process has worked flawlessly when running the macro on Windows 98
SE under Access 97 SR2b on the host machine as a .mdb and also after
being compiled as a .mde and also in Runtime. Additionally, the macro
has run successfully on another Windows 98 SE machine in Runtime with
no Access program installed.

However, after installing the Runtime version on a Windows XP machine
the macro action, for all 3 reports, failed. Why would this happen? I
have decided to change the process from a macro to VBA code instead.
Other than doing this, I don't know of any other options to pursue.

Your assistance in this matter will be appreciated. Thanks, Dalan


Are you sure the problem is Windows XP per se, or is the problem that there is
no default printer?

When you try to print, preview, or export a report, it normally tries to
format for the default printer on the machine and fails with an error if there
isn't one.


Thanks Steve for your response. I kind of had been wondering the same.
I tried, for the first time yesterday, saving the report(s) on another
Windows XP machine, but this time was using VBA code to do the Output
To action and the results were: there were no error messages at all
and the report(s) displayed properly; however, none were saved to
either a floppy disk or the hard drive.

Could this be a default printer formatting problem if the reports are
properly displayed though? I neglected to check or changed the default
printer settings on the Windows XP machine. Since I will be
distributing this database as a runtime version, I obviously need to
minimize issues and potential problems such as the above. I do recall
that the basic reports (with no output action to disks) have printed
okay when I have installed the DB (although it was not the runtime
version) on other machines with different OS's and printers.

Any further thoughts or suggestions will be appreciated. Thanks.
Nov 12 '05 #3

P: n/a
On 6 Jan 2004 00:02:05 -0800, ot***@safe-mail.net (Dalan) wrote:

....
Thanks Steve for your response. I kind of had been wondering the same.
I tried, for the first time yesterday, saving the report(s) on another
Windows XP machine, but this time was using VBA code to do the Output
To action and the results were: there were no error messages at all
and the report(s) displayed properly; however, none were saved to
either a floppy disk or the hard drive.


That blows my theory, then. If there was no default printer, you would have
received errors, and preview would also have failed. Sorry I couldn't be more
help.

Just a shot in the dark, have you tried removing and re-selecting all
references, and recompiling the database on the XP machine? I know folks
often have reference troubles moving an Access database from one OS to
another.
Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.