Margin setting dont hold in A2K Runtime

[SmallTime]

Hi all,

I seem to be loosing my margin settings for reports when running my mde app. on a client machine using A2K Runtime.

I've had a look through the many postings on this subject but didn't find anything relating to the runtime environment.

Anyone know how to overcome this most annoying problem?

 

[dhookom]

Make sure the latest service packs have been installed. A patch job is to set the Name Autocorrect options off.

Duane
MS Access MVP
Find out how to get great answers faq219-2884.

 

[SmallTime]

Many thanks,

Yes, should have mentioned I already have the latest service pack installed on the development machine and I always turn the autocorrect feature off as a matter of course.

Still the margins are changing on the client machine, which is running on A2K runtime.


Regards

 

[dhookom]

The only references I can find are

http://support.microsoft.com/default.aspx?scid=kb;en-us;240826

and

http://support.microsoft.com/default.aspx?scid=KB;EN-US;208912

Duane
MS Access MVP
Find out how to get great answers faq219-2884.

 

[formerTexan]

Alas, I am not going to be a ray of sunshine. Rather I offer this on the hypothesis that misery loves company. And on the off chance that someone else has turned up something new.

The sanguinary website advice to have everyone maintain the same (and unchanging) default ports is not particularly practical in most settings, nor is it particulary accurate. Report margins in A2K can consistantly revert to default anytime there is a change in output destinations (without changing the default) and I have had it occur merely through opening a report to design view.

The obvious solution was to set report margins programmatically at runtime. You can do this using the PrtMips property, but as this is only available in design view, it won't help in MDE versions.

Good luck.

Cheers
Bill

 

[SmallTime]

Thanks Duane, Sorry for the delay in getting back, I've been away. Yes, I did visit these links previously, but as Bill says their not terribly helpful. What Microsoft seems to be suggesting is a poor workaround rather then a true solution.

Many thanks for the pointer(again).

Bill, I'll have a read-up and see if I can crack the PrtMips property (never tried it before). Please correct me if I'm wrong, as I understand it (or want to understand it) If I make all page setting using PrtMips in my original AK2 mdb they'll hold true when I produce an mde running under AK2 runtime. Well, If that's the case it sounds very much like the solution I'm after and I offer you my thanks. If not, please still accept my thanks for your time and effort.

 

[lupins46]

Isn't the runtime package an independent set of runtime files. The patch status of the runtime package is not linked to your normal copy is it? I thought that it was subject to its own patches.

 

[dangleason]

I too have had all of the issues mentioned and tried everything mentioned to date. here is what I can offer that I have not seen yet.
I have a function the I call to set the margins at a value using PrtMips. Yes it is true it has to flip the report into design mode to access the printer settings, and then I flip back to runtime and open the report. I was set to go until I created an MDE. As an MDE you cannot gain access to the printers collection and the function fails. So I am pissed off at MS for this type of sloppiness on such a basic and commonly used feature (margins that is). If anyone gets a solution to this, please let me know..