How to Obtain the Current Instance Handle of an .FLL File

 Last reviewed: December 9, 1995
Article ID: Q115991
The information in this article applies to:
  • Microsoft FoxPro Library Construction Kit, versions 2.5x, 2.6x
  • Professional Edition of Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b

SUMMARY

Within a standard Windows dynamic-link library (DLL), the instance handle of the current .DLL is passed to the function through the LibMain() API function. In a FoxPro-link library (FLL), you do not have access to the LibMain() function.

In FoxPro versions 2.x, you have access to a global variable called Inst. Within this global variable is the current instance handle. However, if you are using Visual FoxPro version 3.0, you can use the FoxPro API call _GetAPIHandle() to obtain the the current instance handle.

MORE INFORMATION

FoxPro 2.x

In FoxPro version 2.x, to obtain the current instance handle, the variable Inst must be declared as follows: 

     HINSTANCE Inst;
Once this is done, the current instance handle will be stored in the global variable Inst.

Visual FoxPro

To obtain the current instance handle in FoxPro version 3.0, use the the FoxPro API call _GetAPIHandle(). For more information on this API function see the _GetAPIHandle() topic in the Visual FoxPro on-line help file.

REFERENCE

Library Construction Kit "Developer's Guide," version 2.5, page 31

Additional reference words: FoxDos FoxWin VFoxWin 2.50 2.50a 2.50b 2.60
2.60a 3.00 3.00b lck api
KBCategory: kbinterop kbtool kbprg kbcode
KBSubcategory:

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: December 9, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.