Hi Alan,

> Unfortunately once in the new VCX it can't seem to find any of the VCX's or forms that are in the EXE.

This is called "project scope". Every executable piece of code remembers from which container file (EXE or APP) it came from. When VFP searches for embedded files (VCX files, images, etc.), VFP only searches within the project scope, that is, the same EXE or APP. With external file the project scope is empty. Visual FoxPro does not search inside any EXE or APP when there is no project scope.

There are other methods of making code visible. For instance, you could load a procedure file with SET PROCEDURE TO or load a programmatic class. This works, because Visual FoxPro searches the PRG based cache before looking for a file. VCXes behave differently, though. As VFP supports multiple classes with the same name when stored in different VCX files, Visual FoxPro bypasses the class list and directly accesses the VCX file.

> My bet is something needs to be changed as a result of making one section longer but I do not know what.

More than one setting. Each line contains the length of the byte code at the very beginning. Every procedure has pointers to various tables relative to the position in the FXP file. Most tables are stored beyond the code and need to be updated. Within the APP there's a directory that has to be updated, as well. All this of course only applies if you haven't encrypted the application or used something like ReFox.