GUID update in Visual Basic .VBP and .FRM files

[smckeown]

Hello,

Can anyone shed some light on the magic that either VBP or Visual Basic performs on GUIDs.

I have a Visual Basic group with an executable, and .OCX. The GUID for the OCX appears in the .frm file along with the .vbp file.

Using VBP, the build step are:
-create a reference copy of the ocx
--set 'no compatilbity' before the build
--update the compatibility directory is checked and set
--set poject to binary comp. after building is set
--update the target executable directory for each project is set

When I run VPB, the ocx is build, the guid is rolled, the .vbp is updated with the new GUID, BUT, the .frm has the old guid.

The executable runs and the project opens fine in Visual Basic, but now there is a guid mismatch between the .frm file and the.vbp file.

Thanks,
Sheryl