Article

Multiple display devices and higher resolutions cause error 4132 in SmartObjects and tools

« Go Back

Information

 
Article Number000012745
EnvironmentWindows
Progress 9.x
OpenEdge 10.0x
Dynamics
Question/Problem Description
Multiple display devices and high display resolutions cause error 4132

Horizontal resolution of display exceeds 1280 pixels

One of the following conditions applies:

Running an ADM2 application which uses the ADM2 smartToolbar.

Running a Dynamics application

Starting the Procedure Editor

Starting the AppBuilder

Opening a Window (.w file) in the AppBuilder

Opening a Dialog-Box in the AppBuilder

Opening a New Procedure window from AppBuilder
Steps to Reproduce
Clarifying Information
Error MessageInvalid character unit value <value>, Changed to 320. (4132)
Defect/Enhancement Number20040302-007
Cause
Resolution
Upgrade to Progress 9.1E01.
 
Upgrade to OpenEdge 10.0B01 or later release.
 
If using Dynamics, upgrade to  Dynamics  2.1B or later release
 
Alternatively, one way to work around the issue is to change the ADM2 (and Dynamics) source code to reference SESSION:HEIGHT and SESSION:WIDTH with NO-ERROR.
Please note that modifying the ADM2 source is neither recommended or supported. However, in cases where there is no alternative the following changes should be considered. 
 
The code below is taken from toolbar.p and provided as an example only.
 
From:
 
IF dMinHeight > 0 AND dMinHeight < (SESSION:HEIGHT - 1) AND
   dMinWidth > 0 AND dMinWidth < (SESSION:WIDTH - 1) AND
   (hWindow:WIDTH < dMinWidth OR hWindow:HEIGHT < dMinHeight) THEN
 
To:
 
ASSIGN locWidth  = SESSION:WIDTH NO-ERROR
       locHeight = SESSION:HEIGHT NO-ERROR.
 
IF dMinHeight > 0 AND dMinHeight < (locHeight - 1) AND
   dMinWidth > 0 AND dMinWidth < (locWidth - 1) AND
   (hWindow:WIDTH < dMinWidth OR hWindow:HEIGHT < dMinHeight) THEN
Workaround
Notes
Note the real issue is a Progress limitation: Although Progress is now on 32-bit platforms, the 320 column restriction is still in place because the r-code structures which store row and column information haven't been updated from 16 bits to 32 bits.
 
The bug fix suppresses the 4132 error messages by adding NO-ERROR where SESSION:WIDTH-CHARS and SESSION:HEIGHT-CHARS attributes are referenced.
References to Written Documentation:
 
Progress Solutions:
P12469, "Expanded/Virtual Screen Resolutions and Progress Limits -- Error 4132"
Attachment 
Last Modified Date9/13/2015 5:42 AM
Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.



Feedback
 
Was this article helpful?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025