XCLN: Distributing Third-Party OCXs & VBXs with Eform .cfg FileLast reviewed: March 31, 1997Article ID: Q154473 |
The information in this article applies to:
SUMMARYIf you add a custom control to a form that is not included with Visual Basic 4.0, this file has to be manually copied to the client computer. As stated in the "Application Designer's Guide" on page 302, you can distribute third-party .ocx and .vbx files by using Microsoft Systems Management Server or other network management tools. You can also accomplish this by adding the custom .ocx or .vbx file to the .cfg file of the Eform.
MORE INFORMATIONTo distribute third-party .ocx and .vbx files, make an entry in the .cfg file as follows:
This should be fine for most executable files, but if a custom control needs its files in the System subdirectory, they will have to be manually copied to the system directory. This is an example: [Platforms] Platform1=Platform1 Platform2=Platform2 Platform3=Platform3 Platform4=Platform4 Platform5=Platform5 Platform6=Platform6 [Platform.Platform1] CPU=ix86 OSVersion=Win3.1 Registry1=LocalServer=%d\!4!J8N&-.EXE File1=!4!J8N&-.EXE File2=<CustomControlFileName>.OCX or .VBX <- This is the Control that is to be copied to the <Windows Directory>\Forms directory. [Platform.Platform2] CPU=ix386 OSVersion=WinNT3.5 Registry1=LocalServer=%d\!4!J8N&-.EXE LinkTo=Platform1 <- With this entry, you do not have the files entries to every platform configuration. NOTE: These FILE= references can also be used for any other file that may need to be copied with the EForm executable files. For instance, any .ini files or any other supporting files can be added in this manner.
REFERENCESFor additional Information about the EForm Configuration File, please refer to Chapter 9, pages 297-302, of the "Application Designer's Guide."
|
Additional query words: forms E-form electronic
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |