For all of you with Paper Size issues
From: cafr2000 (cafr2000_at_discussions.microsoft.com)
Date: 11/10/04
- Next message: Fons Ponsioen: "RE: Setting a Printer in the code"
- Previous message: hermie: "Re: Leader dots in report"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 10 Nov 2004 10:09:08 -0800
I have had a paper size (Legal/Landscape) issue with a report in a .mde
application for some time. After several unsuccessful attempts to find a
solution in the Newsgroups I pestered Microsoft support until I got the
corrrect answer and again an unsuccessful/no solution. The issue involves
something called prtDevMode, this is supposedly some group of control
characters obtained from the print drivers of the default printer. It does
not matter how you have defined the report before converting to a .mde,
Microsoft claims they cannot change the paper size code in the .mde/runtime
application. This situation exists in ALL versions of ACCESS, there are no
service packs that fix it and it has not been fixed in OFFICE/ACCESS 2003 as
MS Support originally tried to tell me. I don't know all of the background
code of course but it does not make sense that you can design a report and
save the page orientation correctly and not the paper size. I was just
notified by MS Support that they cannot create a hot fix and there will
probably not be anything done to correct this. They offered another soultion,
they made reference to some code that will let you set the paper size
programmatically but the catch is it only works in a .mdb. Their solution to
protecting mine and your valuable proprietary source code is to distribute a
password protected .mdb. Now I don't know about any of you but I have gone to
the web and downloaded free password cracking software that is designed
specifically to decode ACCESS passwords and they work very well. Personally I
don't think this is an acceptable solution, I'm sure Microsoft would not
distribute any of their proprietary code this way. I suggest that everyone
that is having an issue with this contact Microsoft support and start a case
regarding this issue. it was my impression that they feel there is not enough
need or concern about this BUG to work on it.
- Next message: Fons Ponsioen: "RE: Setting a Printer in the code"
- Previous message: hermie: "Re: Leader dots in report"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
