Hi!

>DPI-Awarness is nothing VFP 9 deals well.

I found that adding hard coded factor 1.25 to SFPreviewform AddObjectToContainer method fixes the isse for 125% :

* Add the current report object to our output container.

local lcObject, ;
	loObject

with This
	lcObject = 'Object' + transform(recno())
	.oContainer.AddObject(lcObject, .cShapeClass)
	loObject = evaluate('.oContainer.' + lcObject)

* Set properties of the newly added shape. The Width, Height, Top, and Left
* values are 1/10th of the values from the report because those values are in
* 960ths of an inch and the report engine uses a resolution of 96 DPI.

	with loObject
*!*			.Width   = WIDTH/10
*!*			.Height  = HEIGHT/10
*!*			.Top     = TOP/10
*!*			.Left    = LEFT/10

* 28.11.20 Fix for 125% zoom level:
		.Width   = WIDTH/10*1.25
		.Height  = HEIGHT/10*1.25
		.Top     = TOP/10*1.25
		.Left    = LEFT/10*1.25
...

This works only for 125% zoom level. How to find current zoom level in code ?

>VFPA http://www.baiyujia.com/vfpadvanced/f_vfpa_about.asp does better. Try if it helps and if switch to VFPA, VFPA works pretty well so far.

Chen has disassembled and re-assembled vfp9r.dll file.
If I start using it I'm afraid that maybe this is illegar and layers force to stop using it.

VFPA application works in DPI Aware mode (like SetProcessDPIAware is called from VFP application) setting. My application renders barcodes and I read that this setting maked barcodes printed by VFPA application unreadable due to different spacing.