Can't Run SubApp "This is not an application file"

I created a test to run Sub-Apps that run from other applications. When I try to run it, it says "This is not an application file!" I don't understand what I'm doing wrong. Here is what I did:

• I created 2 MFA files. One called "Parent.mfa" the other "Child.mfa"
• "Parent.mfa" has one Frame. It only contains a Sub-App, with source set to "Other Application." Filename set to "Child.ccn"
• "Child.mfa" has one Frame. It contains one String object, which reads "This is a Sub-App. Loading Externally."
  
• I build the "Child.ccn" file. I build the "Parent.exe" file.
  
• If I run the EXE:
  ="This is not an application file!"
  
• If I run the application in MMF2:
  ="This is not an application file!"
  
• I change the Sub-App's File Name Property from "Child.ccn" to its full path name "C:/Test/Child.ccn":
  ="This is not an application file!"
  
• I clear Sub-App File Name to blank. I create Start of Frame event.
  Action: New Application: "Child.ccn"
  ="This is not an application file!"
  
• I change Start of Frame event.
  Action: New Application: Apppath$ + "Child.ccn"
  ="This is not an application file!"

What am I doing wrong? I just don't get it.

Hi JimJam. Did you try clicking "include external files" in the properties.

Marv

Yep, it didn't work.

Ok, so I've redone this program 4 times. I mean completely rebuilt from scratch. New File, new objects, new everything.

After re-doing it the 4th time, it worked. So I've got 4 copies of nearly the same program, and only one of them works...

The other 3 attempts also gave errors. BUT, this doesn't solve my problem. I need to incorporate external sub apps into my current project, which is having the same problem. And I cannot recode it 4 times.

Sorry, I have too much brain leakage for this problem.

Marv

What build are you using? Try choosing an .mfa file for the subapp, and then build your application like normal. It should ask you to build the .ccn file. Click yes, and it should work.

Stephen1980

I was using 248, but then I installed 249 to see if it would fix the issue.

I haven't had the problem after installing 249, but MFA files that were saved in 248 were still having this bug even though I was running the new build.

The bug didn't effect the frames of the application, so I was able to create a new MFA, and then copy all of the frames into it. Then build with 249, and the bug was gone.

But this means that something in the original MFA file was corrupted, because updating the MMF runtime build didn't fix the issue with files created BEFORE the update...

I have isolated the bug and can upload a ZIP file of it all for further investigation if needed.