I believe I have found the solution to this problem. After realizing that it was most likely a windows issue instead of an access issue, I did a little more research. Apparently, this is by design. From the
Microsoft support page I have found this:
Symptoms: After you programmatically change properties of the
Application.Printer object, forms and reports that use the default printer do not automatically inherit these settings.
Cause: Saved forms and reports store printer information as part of their definition. When you preview or print saved forms and reports, these objects use the printer information that is stored within them instead of inheriting the settings from the
Application.Printer object.
Solution: (two possible)
Set the Printer Property to Application.Printer
After you customize the properties for the
Application.Printer object, set the
Printer property of the form or report to the
Application.Printer object. This forces the form or the report to destroy its current
DEVMODE structure and to inherit a new one from the
Application.Printer object.
or
Assign the Printer Settings of the Object Directly
Another workaround is to programmatically set the printer settings of the object itself, instead of setting them to the
Application.Printer property. Setting the individual properties of the object's
Printer property is similar to the user manually changing printer settings within the
Page Setup dialog box. When you programmatically set the object's printer settings directly, the settings are saved with the object automatically.
There is sample code in the help article.
Hopefully this will help someone else too
