The information in this article applies to:
SYMPTOMSAn ActiveX control (.ocx) has been written in Visual C++ that also makes use of the Visual FoxPro Library Construction Kit (LCK) functions. The control may work properly on forms that use the default DataSession but the control fails when the form uses a private DataSession. CAUSELibrary Construction Kit function calls do not occur in the DataSession context of the form that made the call to the .ocx. There is only one global context in which the Library Construction Kit function can call into Visual FoxPro, no matter where the call originated. RESOLUTION
If a private DataSession is necessary, write the ActiveX control completely
in Visual C++ or Visual Basic and expose properties and methods that can be
accessed by Visual FoxPro.
STATUSThis behavior is by design. MORE INFORMATION
FoxPro and Visual FoxPro have included the Library Construction Kit for
many versions. The Library Construction Kit functions allow developers to
write libraries in C that can be loaded by FoxPro or Visual FoxPro to
extend its functionality by accessing the FoxPro API. Starting with Visual
FoxPro version 5.0, the Developer's Guide has included information to help
developers get a start on creating ActiveX controls to access the Visual
FoxPro API. ActiveX controls can make use of the LCK functions if used
within the global context of Visual FoxPro.
REFERENCES
Microsoft Visual FoxPro "Developer's Guide," version 5.0, pages 645-647.
Additional query words:
Keywords : kbVFp kbVFp500 kbVFp600 FxprgGeneral FxtoolLck |
Last Reviewed: December 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |