Select a link below to view the information on the given problem.
Problem 1: After a successful conversion and compilation, there is a link error.
Problem 2: At the time a form
is loaded, there is a debug message that there is no shared
resource for template number ###.
Problem 3: Windows 95 Users get CreateProcess Failed due to 0 during conversion.
Problem 4: Unable to compile VBBElib under Visual Studio 5.0 compiler due to
error in DirListBox.cpp
Problem 5: Unable to compile
VBBElib under Developer Studio 4.0 compiler due to errors in
vbvar.cpp.
Problem 6: At startup of conversion the message: Wrong Version Of Run-time DLL
appears.
Problem 7: Failure to convert
a VB.Net project.
Knowledge Base Item #1
Date: April 1, 1997
Problem:
After a successful conversion and compilation, there is a link
error.
Status:
Resolved
Cause:
Microsoft's compiler releases 4.0 and 4.2 and 5.0 have incompatible
libraries. The version of the library that ships with the converter
is linked with MFC 4.2.
Quick Fix:
- Open the VBBELIB.mdp file in the skeldir directory.
- Select Rebuild All.
This will create a library for you which is compatible with
your release of the compiler and the libraries you are using.
^ Back To Index ^
Knowledge Base Item #2
Date: April 1, 1997
Problem:
At the time a form is loaded, there is a debug message that
there is no shared resource for template number ###.
Status:
Resolved
Cause:
The VB model for MDI child windows is different than that of
MFC.
Quick Fix:
None. This is not an error. It is a warning that there is no
shared menu and as such is true. It does not cause the application
to fail.
^ Back To Index
^
Knowledge Base Item #3
Date: May 22, 1997
Problem:
Windows 95 Users get CreateProcess Failed due to 0 during conversion.
Status:
Resolved
Cause:
CreateProcess on Windows 95 for some users is not ignoring the
Security Attributes. This is fixed for all users.
Quick Fix:
None. Contact us for a release update.
^ Back To Index ^
Knowledge Base Item #4
Date: September 23, 1997
Problem:
Unable to compile VBBElib under Visual Studio 5.0 compiler due
to error in DirListBox.cpp.
Status:
Resolved
Cause:
Microsoft C compilers 4.2 and 5.0 compile the same line differently.
Quick Fix:
Change the line below to add a cast to (int &). Hence,
change:
DirListBox_AddSubtree(sPath, TempLocn(iElements + 1) );
to:
DirListBox_AddSubtree(sPath, (int &)TempLocn(iElements
+ 1) );
^ Back To Index ^
Knowledge Base Item #5
Date: September 23, 1997
Problem:
Unable to compile VBBElib under Developer Studio 4.0 compiler
due to errors in vbvar.cpp.
Status:
Resolved
Cause:
Microsoft C compilers 1.xx, 2.xx, 4.0, 4.2 and 5.0 have different
COleVariant classes and definitions for boolean and restricted
symbol definitions.
Quick Fix:
Upgrade to Version 4.2 or higher of the C compiler.
^ Back To Index ^
Knowledge Base Item #6
Date: September 23, 1997
Problem:
At startup of conversion the message: Wrong Version Of Run-time
DLL appears.
Status:
Resolved
Cause:
The converter was built with Microsoft Visual Basic and service
pack 2 installed. The installer took the most cautious approach
during installation and did not overwrite anything. It now does
a version check during the installation.
Quick Fix:
Reinstall with the latest version or apply the service pack.
^ Back To Index ^
Knowledge
Base Item #7
Date: January 1, 2003
Problem:
Failure to convert a VB.Net project.
Status:
No Resolution
Cause:
The converter was built for Microsoft Visual Basic versions
3 through 6. After version 6, the language and environment
changed so drastically that it was no longer possible to adapt
the converter.
Quick Fix:
None
^ Back To Index ^
FAQ
VB To C++ Converter Questions
Question: How much does it cost? What does it do?
Answer: Look
on our products page right here for what it does and what it
costs. Look on our Limits Page for what it does not do.
Question: What versions are supported?
Answer: Versions 3,4,5, and 6 are supported.
Some of the features are not yet supported. If
you
have
a problem
as
a result of those features we will
make every effort to get you a fix quickly. You have 1 year from the
time you purchase the product to submit and receive free
upgrades via e-mail.
Question: I have a bug...
Answer: Look in our Knowledge Base right here.
^ Top Of Page ^
