M
Maver1ck666
I have a problem with Access 2003 Im hoping you can help me with.
I have created a user database which displays a number of reports based on
statistics a number of users input. When some users try and dislpay the
reports, they get the error message 'The expression After Update you entered
as the event property setting produced the following error: The OpenReport
action was cancelled'.
Here's the strange thing! The database is installed on a number of users PC
and it works for some of them.
I have narrowed it down to the type of printer being installed on the users
PC and specificy the printer model 'HP LaserJet 8100 Series PCL 5e'. If I
remove the printer completely from the users PC and make the image writer the
default printer, the reports will work but as soon as I reinstall it, they
dont. Unfortunately, my company employs over 1000 people and have over 15
different printer models so we cant just change the culprit printers.
The database was built in A03 and comprises of a front-end, back-end and an
..mde which is packaged with a runtime and deployed via an msi using Active
Directory.
Has anyone ever come across this kind of problem before? I have spent ages
searching Google and MSKB to no avail!
Thanks in advance for your help!
Mav
I have created a user database which displays a number of reports based on
statistics a number of users input. When some users try and dislpay the
reports, they get the error message 'The expression After Update you entered
as the event property setting produced the following error: The OpenReport
action was cancelled'.
Here's the strange thing! The database is installed on a number of users PC
and it works for some of them.
I have narrowed it down to the type of printer being installed on the users
PC and specificy the printer model 'HP LaserJet 8100 Series PCL 5e'. If I
remove the printer completely from the users PC and make the image writer the
default printer, the reports will work but as soon as I reinstall it, they
dont. Unfortunately, my company employs over 1000 people and have over 15
different printer models so we cant just change the culprit printers.
The database was built in A03 and comprises of a front-end, back-end and an
..mde which is packaged with a runtime and deployed via an msi using Active
Directory.
Has anyone ever come across this kind of problem before? I have spent ages
searching Google and MSKB to no avail!
Thanks in advance for your help!
Mav