Jumat, 17 Agustus 2012

[MS_AccessPros] Re: Assigning printing setting through API

 

Steve, thanks, I admit I have never used Acc2003, so can't really tell, but this property surely does not exist in Acc2010. Checked hidden members in Object browser, not listed, tried to reference it in a code, same thing, I receive Application-defined or object-defined error.

My quest continues...

And all I wanted to do is to easily and directly replace prtDevMode property with one on hand and ready, in what's suggested way of use, compiled state (.accde). In the end, the only way for me to do it is to modify system printer and assign it to report, in reality doing same thing, just WAY slower and doing 2 extra (and unnecessary) steps.

Miroslav

--- In MS_Access_Professionals@yahoogroups.com, Steve Conklin <StephenMConklin@...> wrote:
>
> The Report's paper property does not show up in intellisense (maybe it did in ver 2003?), but it does compile. That's how I get my Invoice to print to paper size 169, for example.I understand that the report size should not be changed at run-time, but the report is designed to the spec's of the custom paper isn't it? Steve

> To: MS_Access_Professionals@yahoogroups.com
> From: mirkosluv@...
> Date: Fri, 17 Aug 2012 05:22:02 +0000
> Subject: [MS_AccessPros] Re: Assigning printing setting through API
>
>
>
> Dear Steve, many many thanks for taking your time with this issue. Although, for many reasons, we can't use any solution that would modify report size itself, I'm still puzzled what you meant with below line?
>
>
>
> > rpt.Paper = AppPropLookup("InvoicePaper")
>
>
>
> There's no "Paper" property of an report object, can you explain?
>
>
>
> Again, many thanks
>
>
>
> Miroslav
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>

__._,_.___
Recent Activity:
.

__,_._,___

Tidak ada komentar:

Posting Komentar