J
Jedi
First, let me say that I have done my due diligence and researched this
error till the cows came home. Unfortunatly, with one exception, the
resolutions all seem to point to an issue with either a coding mistake
or a null data report. In my case, it does not seem to be either.
The brief synopsis of the problem:
Within one of my Access 2003 databases, I have a function which opens a
report for either preview or print. On my system, the report is
generated correctly, with no errors. Once the database is deployed to
a client computer I am finding that the OpenReport call is causing an
Error 2501.
Now, here is where it gets really strange. In my searching, I found
one reference to this being related to the HP Laserjet 5 series of
drivers. So I decided to test this theory out. I changed the default
driver to something other then the HP Laserjet driver and... (trumpets
sounding...) the report was generated perfectly. Therefore, I am
guessing that the information I found was on the right track.
I have played around with several different HP Drivers, but every
single one of them seems to cause this error. My question to the group
is this:
Has anyone else run up against this problem? If so, what have you been
able to do to resolve it? (Changing the users default printer is NOT a
valid option.)
Thanks in Advance!
-Jedi
error till the cows came home. Unfortunatly, with one exception, the
resolutions all seem to point to an issue with either a coding mistake
or a null data report. In my case, it does not seem to be either.
The brief synopsis of the problem:
Within one of my Access 2003 databases, I have a function which opens a
report for either preview or print. On my system, the report is
generated correctly, with no errors. Once the database is deployed to
a client computer I am finding that the OpenReport call is causing an
Error 2501.
Now, here is where it gets really strange. In my searching, I found
one reference to this being related to the HP Laserjet 5 series of
drivers. So I decided to test this theory out. I changed the default
driver to something other then the HP Laserjet driver and... (trumpets
sounding...) the report was generated perfectly. Therefore, I am
guessing that the information I found was on the right track.
I have played around with several different HP Drivers, but every
single one of them seems to cause this error. My question to the group
is this:
Has anyone else run up against this problem? If so, what have you been
able to do to resolve it? (Changing the users default printer is NOT a
valid option.)
Thanks in Advance!
-Jedi