B
Brian
The preview of certain reports appears very large, as though Access increased
the font size by 400%. This is not a zoom issue; the report actually prints
this way - a one-page report spreading across four or more pages with very
large fonts.
I discovered that it occurs only when the PC running the app has certain
default printers when the report is opened; namely, the HP LaserJet 4050TN
and LaserJet 2200. These are the two on my clients' systems that have the
problem, although there are probably many others on the computers of
potential clients, just waiting for my app to arrive so they can make me look
like an idiot. If I switch the client to a different default printer, then
the problem does not occur.
Once the client previews the report (and it appears incorrectly), the client
can change from landscape to portrait and back again, and the problem will
not reappear for that report until I issue an updated version of the front
end, at which time the entire thing repeats itself. This pretty much makes me
look like an idiot to my clients - I spend hundreds of hours developing a
sophisticated app, and I have to tell them to switch to portrait & back to
fix certain reports with every update to the FE that I release!
I called MS Access support, and their answer is that some of the current
default printer driver information is (by design) stored with the report when
it is created (not when saved subsequently), so I should simply set my
development machine to default to Generic / Text Only every time I create a
form. I generally keep my default printer set as Adobe PDF, since I use that
far more than any other printer.
I can hardly believe that I am the only one that has experienced this, and
the evident fix is pretty ugly: re-create every report in my app while I have
the default printer set to Generic / Text only.
Four questions:
1. Why does it seem like nobody else has this problem?
2. Is the only fix really to recreate all my reports? Is there perhaps a way
to programmatically reset that driver info?
3. Is this just Access, or is this standard on other dev platforms?
4. I know I can hardly challenge Microsoft on this, but is it realistic to
keep one's default printer set to Generic / Text only just to ensure that the
correct printer driver information is embedded in the report?
the font size by 400%. This is not a zoom issue; the report actually prints
this way - a one-page report spreading across four or more pages with very
large fonts.
I discovered that it occurs only when the PC running the app has certain
default printers when the report is opened; namely, the HP LaserJet 4050TN
and LaserJet 2200. These are the two on my clients' systems that have the
problem, although there are probably many others on the computers of
potential clients, just waiting for my app to arrive so they can make me look
like an idiot. If I switch the client to a different default printer, then
the problem does not occur.
Once the client previews the report (and it appears incorrectly), the client
can change from landscape to portrait and back again, and the problem will
not reappear for that report until I issue an updated version of the front
end, at which time the entire thing repeats itself. This pretty much makes me
look like an idiot to my clients - I spend hundreds of hours developing a
sophisticated app, and I have to tell them to switch to portrait & back to
fix certain reports with every update to the FE that I release!
I called MS Access support, and their answer is that some of the current
default printer driver information is (by design) stored with the report when
it is created (not when saved subsequently), so I should simply set my
development machine to default to Generic / Text Only every time I create a
form. I generally keep my default printer set as Adobe PDF, since I use that
far more than any other printer.
I can hardly believe that I am the only one that has experienced this, and
the evident fix is pretty ugly: re-create every report in my app while I have
the default printer set to Generic / Text only.
Four questions:
1. Why does it seem like nobody else has this problem?
2. Is the only fix really to recreate all my reports? Is there perhaps a way
to programmatically reset that driver info?
3. Is this just Access, or is this standard on other dev platforms?
4. I know I can hardly challenge Microsoft on this, but is it realistic to
keep one's default printer set to Generic / Text only just to ensure that the
correct printer driver information is embedded in the report?