How do I find a Microsoft Forms 2.0 Control in a VC6 Project? [modified]
-
The better question might be, "How can I get rid of this dependency?". I'm finishing testing on another developer's project who doesn't know himself how he got his application dependent on the FM20.dll and FM20ENU.DLL. Looking online I found that these are Microsoft forms 2.0 controls. Is there a way to check the resources or the project, for 2.0 controls? Since, these are not redistributable and the application is not dependent on anything that MS Office might have installed (as far as we know), I want to get rid of this dependency but simply removing the dlls from the application's installation directory is not going to solve this problem. I need to know why the application is dependent on them. Is there certain 2.0 API type calls that I can search on within the project? Or something inside of the IDE itself that I can check?
modified on Tuesday, March 29, 2011 3:24 PM
-
The better question might be, "How can I get rid of this dependency?". I'm finishing testing on another developer's project who doesn't know himself how he got his application dependent on the FM20.dll and FM20ENU.DLL. Looking online I found that these are Microsoft forms 2.0 controls. Is there a way to check the resources or the project, for 2.0 controls? Since, these are not redistributable and the application is not dependent on anything that MS Office might have installed (as far as we know), I want to get rid of this dependency but simply removing the dlls from the application's installation directory is not going to solve this problem. I need to know why the application is dependent on them. Is there certain 2.0 API type calls that I can search on within the project? Or something inside of the IDE itself that I can check?
modified on Tuesday, March 29, 2011 3:24 PM
In VC6, the two ways that a project links to a DLL is: 1. It includes some .h header file, and that has a statement like
#pragma comment(lib, "bozo.lib")
2. It links directly by specifying the .lib file explicitly in the Linker options.
Best wishes, Hans
-
In VC6, the two ways that a project links to a DLL is: 1. It includes some .h header file, and that has a statement like
#pragma comment(lib, "bozo.lib")
2. It links directly by specifying the .lib file explicitly in the Linker options.
Best wishes, Hans
Thanks, Hans. I've never used the #pragma comment lib directive. I've checked for both and there are no inclusion to those libs. The only thing it may be, and I will have to check first, is that he includes explicitly two libraries, that he created, in the Linker options. Perhaps, one or both of those library projects use the forms controls.
-
In VC6, the two ways that a project links to a DLL is: 1. It includes some .h header file, and that has a statement like
#pragma comment(lib, "bozo.lib")
2. It links directly by specifying the .lib file explicitly in the Linker options.
Best wishes, Hans
Okay, checking for a linked library in a library project when none will exist makes sense. I don't know what I was thinking. But it didn't have any #pragma comment(lib,...) directives in the two libraries either. FYI, I finally found the answer by viewing the .rc resource file. It seems that a GUID exists, because the Forms Controls (is a COM object or OLE server?), for each of the controls that were used within the project. Found 4 GUIDs, one image, one text box, and two labels. Now have to replace them. Apparently they were used because the items all needed image backgrounds.