dkulikow
15th May 2012, 23:21
Hello,

I was wondering if anyone has experienced any issues with Baan printing from a client with Windows 7 (64 BIT).

We have found that all OS levels of Windows up to Windows 7 (32 BIT) work fine and use the defined font settings (custom user fonts/Baan stnd). However, we have select few users that get totally different font settings results from the Windows 7 (64 BIT) system.

In all cases the font is larger than the Baan defined, as well as, the font spacing is larger. This results in some information that should have printed on the page doesn't print. It doesn't auto move what it couldn't fit to the next page either. Some users may not realize that they are only seeing a portion of their report data.

We currently have our database and app server running on virtual machines with SQL 2008 and Windows Server 2008. I've updated my BW client to the latest version available (103). We run Baan IV c4 NAS0 w/SP19 as our last service pack loaded.

Thanks!
dkulikow

andreas.toepper
16th May 2012, 08:16
We have some printing-issues with LN, too. Infor has introduced a new parameter to scale the output onto the selected page-format, when printing with bwprint.exe:

-set WINFONTCORR=1

Using this setting the output will fit on the selected pageformat. (It will even scale a landmark output to fit on a normal page.)

I havn't check wether this works on BaanIV but Infor KB 699923 lists it for BannIVc and BaanIVb, too.

Kind regards
Andreas

dkulikow
17th May 2012, 15:50
Andreas,

Thank you for your reply. I did try the setting, but it didn't seem to make any difference.

What I've learned since logging my thread is that there is a separate directory for 64 Bit machines in the registry settings called Wow6432Node. It's there that it appears to be holding my setting when I set the fonts manually.

So, I have my machine working now. My current problem is that even though I export the settings and then import them into another system with 64 Bit it doesn't find the changes.

I'll make sure to update this thread when we do finally figure this out as I'm sure others will encounter the same issues at some point.

Thank you!
dkulikow

cherianka
21st October 2014, 19:43
Has any one found a solution to this yet?