B
Brad Janisch
I have created a reporting tool within Access 97 from
which users will run a series of reports from Access
Runtime. A recent request from one of my users was made
to produce the reports in a format that could be e-
mailed. As a result, I decided to create a simple "Output
To" macro that saves and displays the report in Snapshot.
Everything seemed to work great until my user group got a
hold of it.
The problem is every time the users who are on Runtime
try to execute the macro that outputs the reports to
Snapshot, they receive an "Action Failed" message. I have
tested the macros out on 5 machines that have Runtime and
5 machines that have Access 97. The only ones that fail
are the machines with Runtime. I haven't been able to
find anything in the MS KB or on the community board to
indicate there is a conflict between Runtime and
Snapshot, so I have no idea where to turn.
Does anyone have any idea why the "Output To" macro would
not work on Runtime?
After reading many of the post over the last month, I
understand another approach may be to create the report
as a PDF. I do not know SQL or code and was wondering if
anyone could tell me how (step by step, if possible) I
could approach this as a solution.
Thanks a million
Brad
which users will run a series of reports from Access
Runtime. A recent request from one of my users was made
to produce the reports in a format that could be e-
mailed. As a result, I decided to create a simple "Output
To" macro that saves and displays the report in Snapshot.
Everything seemed to work great until my user group got a
hold of it.
The problem is every time the users who are on Runtime
try to execute the macro that outputs the reports to
Snapshot, they receive an "Action Failed" message. I have
tested the macros out on 5 machines that have Runtime and
5 machines that have Access 97. The only ones that fail
are the machines with Runtime. I haven't been able to
find anything in the MS KB or on the community board to
indicate there is a conflict between Runtime and
Snapshot, so I have no idea where to turn.
Does anyone have any idea why the "Output To" macro would
not work on Runtime?
After reading many of the post over the last month, I
understand another approach may be to create the report
as a PDF. I do not know SQL or code and was wondering if
anyone could tell me how (step by step, if possible) I
could approach this as a solution.
Thanks a million
Brad