I am having a weird problem with a client using AREV64 as an MDI_CHILD. I have an MDI Frame that has a Create Quick Event as follows:

Quick Event

Options: Start an MDI child form

Has priority: No

Event Action

Type: Execute a stored procedure

Target: START_MDICHILD

Message: EXECUTE

Prams: 'AREV64_CHILD_FORM','@MDIFRAME','AREV64'

I also have an event script on the CREATE event that sets some MDI_FRAME menu items to invisible.

When I run the system, I can resize the MDI Frame as well as the MDI Client, all works as expected.

The Problem

1. When I start up the window on my development system, all works fine.

2. When I start up the window on an RDP session into the client's server, all works fine.

3. When a user starts up the MDI Frame it is not sizable and the AREV64_CHILD_FORM is extremely large and does not fit into the child frame. Shows about 1/3 of the left side of the AREV64 screen and about 3/4 of height and is a highly scaled font. Only happens on the users screens. They are in the same office as the server and directly connect with ClientSetup.exe run numerous times as Admin user.

I have tried setting the Sizable property of the window to every setting possible, same results.

I have tried setting the DPI to 1 in the RXI to no avail.

Any ideas out there? Has anyone seen this? Any suggestions?

Running the AREV64 standalone form works just fine and can be resized and this is what is being done until I can figure out the problem.

Thanks,

Greg Helland

BleuPelikan, Inc.

Some more information that might help.

My desktop resolution and my customer's server desktop resolution is 4536x2590. All works fine.

The users on the customer's network have desktop resolutions of 1920x1080 and this is the highest they can go. Maxed out.

The MDI Frame resizes perfectly to accommodate 1920x1080 but the MDI Child is massivly big and does not change. Can't get to an anchor point to resize the AREV64 child form either.

I tried starting the MDI Child with:

SW_SHOWNORMAL$

SW_RESTORE$

SW_SHOWMINIMIZED$

Nothing changes on the 1920x1080 screens but on the 4536x2590 screens each of these creates expected behavior.

Hope that helps. I appreciate it!

Greg

This is likely because your screen resolution is different than theirs. Try setting your screen resolution to their screen resolution, resaving the screens and seeing if that sorts it.

I see all sorts of issues with this when working remotely on a Surface and then returning to the desktop. Menus become large etc etc.

The Sprezzatura Group

The Sprezzatura Blog

World leaders in all things RevSoft

Hi, Greg.

The screen coordinates for the AREV64 window are pulled from the user configuration record, I believe. I'm a little confused because in OI 10.x the configuration record is user and machine specific, so I'm not certain how the "bad" information got into the record from your system - however, the configuration record does walk "up the chain" looking for a configuration record when it's started, so perhaps that explains it.

In either case, you can "clean out" those values by starting up OI's IDE in the customer's application, on the machine that is having the problem, and typing in the following:

RTI_IDE_CFG "SETVALUE",200,""

200 is the location in the configuration record for the CTO/AREV64 window information - you can find this out by looking at the RTI_IDE_CFG_EQUATES insert, and finding the value for IDE_CFG_POS_CTO_SIZE$.

To write the (now-blank) value out, you'd then issue the following command:

RTI_IDE_CFG "FLUSH"

Give that a try and see if it works for you?

- Bryan Shumsky

Revelation Software, Inc.

Bryan,

This worked perfectly! Thanks so much.

Also, thanks Andrew for answering me as well.

It is all appreciated,

Greg

View this thread on the Works forum...