Microsoft KB Archive/162119

= PRB: Some Visual J++ Samples Report Errors when Compiling =

Article ID: 162119

Article Last Modified on 5/12/2007

-

APPLIES TO


 * Microsoft Visual J++ 1.0 Standard Edition
 * Microsoft Visual J++ 1.1 Standard Edition

-



This article was previously published under Q162119



SYMPTOMS
Compiling some of the samples on the Visual J++ CD may result in the following error messages.

JavaCallingCOM
C:\Msdev\samples\microsoft\javacallingcom\usecom.java(10,8) : error J0051: Undefined package 'comserver'

OLEControls
C:\Msdev\samples\microsoft\olecontrols\orgchart.java(8,8) : error J0051: Undefined package 'msoutl32'

HTMLControls
C:\Msdev\samples\microsoft\htmlcontrols\updatecontrols.java(7,8) : error J0051: Undefined package 'intrinsc'

DAOSample
C:\Msdev\samples\microsoft\daosample\dao_dbengine.java(3,8) : error J0049: Undefined name 'dao3032._DBEngine'

C:\Msdev\samples\microsoft\daosample\simpledao.java(12,8) : error J0051: Undefined package 'dao3032'

RDOSample
C:\Msdev\samples\microsoft\rdosample\simplerdo.java(9,8) : error J0051: Undefined package 'msrdo32'

COMCallingJav
C:\Msdev\samples\microsoft\comcallingjava\euclid.java(8,8) : error J0051: Undefined package 'euclid'

CabAndSign
C:\Msdev\samples\microsoft\cabandsign\javabeep.java(31,2) : error J0049: Undefined name 'IBeeper'



CAUSE
The samples listed above all require Java descriptions of the COM components they use. The build errors are generated if the Visual J++ Java Typelib Conversion Utility is not run on the type library required by the samples.



RESOLUTION
You can create the Java description of COM components by running the Java Type Library Wizard from within the IDE under menu Tools.Java Type Library Wizard, or by running JavaTlb.exe from an MS-DOS command line.

Help and the Readme.html for the samples listed above describe the steps required to successfully compile and run the samples. Following the steps described in Help and each individual Readme.html file for the specific sample should resolve the errors. You can find the Readme.html file in the directory where each individual sample is located.

The Readme.html also has information that should help in troubleshooting problems with the specific sample.



STATUS
This behavior is by design.

