DOCUMENT:Q193016  23-SEP-1998  [vbwin]
TITLE   :PRB: Error Compiling VB5 Project Using LPVOID in Type Library
PRODUCT :Microsoft Visual Basic for Windows
PROD/VER:WINDOWS:6.0
OPER/SYS:WINDOWS
KEYWORDS:

======================================================================
---------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Visual Basic Learning, Professional, and Enterprise Editions
   for Windows, version 6.0
---------------------------------------------------------------------

SYMPTOMS
========

While compiling a Visual Basic 5.0 project in Visual Basic 6.0, if the
Visual Basic 5.0 project uses a type library that has a function that
returns a LPVOID or a structure that contains a LPVOID field, the following
error occurs:

   Compile Error : Variable uses an Automation type not supported in Visual
   Basic

CAUSE
=====

LPVOID is a Typedef to "void *." Visual Basic 6.0 is changed to explicitly
prohibit the use of pointers in structures and as function return values.

RESOLUTION
==========

Avoid using LPVOID as a field in a structure or as a return value in the
type library. Instead, change them to type LONG respectively.

NOTE: Do not change the Typedef for LPVOID to LONG, because that would
change the meaning of LPVOID in function parameters where it is valid and
desirable.

STATUS
======

This behavior is by design.

Additional query words: kbdss kbDSupport kbVBp kbVBp600 kbCompiler
======================================================================
Version           : WINDOWS:6.0
Platform          : WINDOWS
Issue type        : kbprb

=============================================================================

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.

Copyright Microsoft Corporation 1998.