Skip to main content

This article explains what to do if the Appmaster Builder screen painter is displaying a blank screen even though the screen previously had been coded.

Problem:

When you double-click the mouse on a screen to edit the source, you are presented with a blank screen, even though you know the screen should be there.

Resolution:

You can determine the cause of this problem by trying the following:


  • Determine if the screen file exists. On the Options > User Preferences > Project tab, determine the path to the project. Open Windows Explorer or a browser at that location and examine the APSSCRN folder to make sure the file exists.
  • If the screen file does exist, compare the file content to another member in the APSSCRN folder to ensure that something has not overlaid your screen.
  • If all of the file attributes are correct, determine if an older version of the software exists on the machine and is getting put into the run-time environment.

In this case, an older version of the MFE-EE 3.0 (AMB Desktop) software was installed on a machine that previously had a much newer version installed. This caused windows to place shared DLL files from the older version into the run-time environment. You can do either of the following to resolve this issue:


  • Uninstall the older version of the software.
  • Ensure that the newer version was the last version to be installed.

Incident Number: 2279799






Date:

Name:

Description of change:
Date:

Name:

Description of change:

Old KB# 14354

#EnterpriseDeveloper
#MFDS