David,
I'm still testing in the mdb on my development PC and I can't get it to work
there.
Hopefully, if I can get it to work in the mdb, it will (might) work in the
mde at the client site.
That's my goal anyway.
I still haven't heard from anyone who has successfully done so in either
file form.

--
Bob Darlington
Brisbane
"David-W-Fenton" <NoEmail (AT) SeeSignature (DOT) invalid> wrote

Hi Bob,
I have the similar problem, so far I did what Tony suggested, I go to
client place, setup CUSTOM page on server properties, open my report
in design mode, change pagesize as CUSTOM and recompile it, so far
it's ok, but I prefer to do once a time so I use this way, I put my
report on backend database so you just set once for the custom page
then I call that report from my frontend so now everytime I copy my
modified fron'tend, I don't need to set the pagesize in my client
place even I can email it...but this doesn't works if I use Ms Access
Runtime in my client place
HTH

Yanto

On Oct 22, 7:45*am, "Bob Darlington" <b... (AT) notheredpcman (DOT) com.au>
wrote:

On 23/10/2010 09:01:00, yanto wrote:
Have you tried the old fashioned method (AK2) using things like PRTMIP &
DEVMODE?

Phil

Phil,
The app is distributed as an mde.

--
Bob Darlington
Brisbane
"Phil" <phil (AT) stantonfamily (DOT) co.uk> wrote

Thanks Yanto.
Unfortunately, I have a mixture of runtime and non runtime installations.
I hadn't thought about attaching the report to the backend though, so I'll
have a play with that idea.

--
Bob Darlington
Brisbane
"yanto" <yanto2000 (AT) gmail (DOT) com> wrote

Hi Bob,
I have the similar problem, so far I did what Tony suggested, I go to
client place, setup CUSTOM page on server properties, open my report
in design mode, change pagesize as CUSTOM and recompile it, so far
it's ok, but I prefer to do once a time so I use this way, I put my
report on backend database so you just set once for the custom page
then I call that report from my frontend so now everytime I copy my
modified fron'tend, I don't need to set the pagesize in my client
place even I can email it...but this doesn't works if I use Ms Access
Runtime in my client place
HTH

Yanto

On Oct 22, 7:45 am, "Bob Darlington" <b... (AT) notheredpcman (DOT) com.au>
wrote:

On 24/10/2010 23:33:04, "Bob Darlington" wrote:
Don't think that is a problem

Phil

Phil,
I thought that those methods required the reports to be able to be opened in
design mode, which you can't do in mde.

--
Bob Darlington
Brisbane
"Phil" <phil (AT) stantonfamily (DOT) co.uk> wrote

On 25/10/2010 01:02:12, "Bob Darlington" wrote:
Er um deep crimson

Of course you're right

apologies

Phil

Thanks to all for their help on this one.
I've reluctantly come to the conclusion that I can't use the Printer object
to reset a custom paper page size after migrating my front end to the client
PCs, so I've given up on that tack.
Instead, I moved along the line suggested by Yanto (in this thread) and
created a new db to hold the Cheque report with attendant queries, linked
relevant tables to the backend db and loaded it into the user's 'CurrentDir'
folder.
I can then open it with OpenCurrentDatabase as follows:

Set objAccess = New Access.Application
With objAccess
lngRet = apiSetForegroundWindow(.hWndAccessApp)
lngRet = apiShowWindow(.hWndAccessApp, SW_NORMAL)
lngRet = apiShowWindow(.hWndAccessApp, SW_MAXIMIZE)
.OpenCurrentDatabase CurrentDir & "cheques.mdb"
.DoCmd.OpenReport strReport, acViewPreview, , , , gblPropNum
End With


--
Bob Darlington
Brisbane
"Bob Darlington" <bob (AT) notheredpcman (DOT) com.au> wrote