True that. The reason Access works internally in TWIPS is because Access doesn't draw anything. It passes it to a WINDOWS renderer that looks at the sizes and interacts with the screen's resolution settings. This all happens internal to the O/S.
That is, of course, due to the fact that every potential visual output device can have different resolution. Your printer is typically either 200, 300, or 600 dots per inch. Your video screen is some number of pixels high and wide depending on what video card you bought. If you have TWO monitors, they can be different models with different resolutions. Access would never be able to be THAT versatile - but it's OK because they don't have to reinvent that particular wheel. Windows has it covered already.
So as has been said, the question isn't how many inches across - it is how many PIXELS across that will matter, and that depends on the video card, not on the screen.
By the way, Colin (and anyone else), the reason for the limit of 22.75 inches for screen dimensions is a hold-over from early Windows days. The Access folks (and maybe Windows itself) have never upgraded the drawing code. You would figure it out really quickly if you did the math.
One twip is the smallest distance or size you can specify in any Access sizing or placement operation. If you look it up, one twip is defined as having 1440 twips per inch. That way, YOU don't have to diddle in absolute pixels, only in "virtual" pixels. So...
22.75 inches x 1440 twips per inch = 32760 twips width. And of course if you remember your binary scaling, 32767 is the largest possible positive integer in 16-bit terms. So their bloody scaling system still apparently works in INTEGER (vs. LONG) variables.
