G
Guest
I have a thread from late February on this topic, and still have not gotten it resovled.
I'm hoping someone can assist with this, since it is holding us us in upgrading our in house db front end from Access 97 to Access 2003
In a nut shell, landscape reports are either dislplaying correctly and printing portrait, or displaying and printing portrait, (when they should be landscape)
Today I tested one system printing to an HP 2200, and it exhibited the above problem. However, the same system printing the same report to an HP 5SI printed correctly
The Access 97 version of this database never had any such issues. I have tried all kinds of things from recreating the reports, turning off autocorrect, and much more (this has been going on for over a month now), and I have also seen messages from others experiencing this same problem. I am left with the suspicion this is a bug in Access, since it occurs randomly (or so it seems)
It is somewhat frustrating as I have an Access 2003 runtime ready to go, and around 75 users waiting for it. However, I feel like I would be asking for trouble rolling this out with the potential of many users having problems with their reports
If anyone has any suggestions or can help in any way, I'd be most grateful
The previous thread, which is not getting a response, has the subject "Strange Printer behavior"
Thanks for any help
Tom
I'm hoping someone can assist with this, since it is holding us us in upgrading our in house db front end from Access 97 to Access 2003
In a nut shell, landscape reports are either dislplaying correctly and printing portrait, or displaying and printing portrait, (when they should be landscape)
Today I tested one system printing to an HP 2200, and it exhibited the above problem. However, the same system printing the same report to an HP 5SI printed correctly
The Access 97 version of this database never had any such issues. I have tried all kinds of things from recreating the reports, turning off autocorrect, and much more (this has been going on for over a month now), and I have also seen messages from others experiencing this same problem. I am left with the suspicion this is a bug in Access, since it occurs randomly (or so it seems)
It is somewhat frustrating as I have an Access 2003 runtime ready to go, and around 75 users waiting for it. However, I feel like I would be asking for trouble rolling this out with the potential of many users having problems with their reports
If anyone has any suggestions or can help in any way, I'd be most grateful
The previous thread, which is not getting a response, has the subject "Strange Printer behavior"
Thanks for any help
Tom