jonesrw
asked on
Upgrade from VB3 to VB5.
I am upgrading a medium sized application from VB3 to VB5. Are there any known issues/problems that I should look out for? In particular I am using a lot of data access code (createsnapshot etc) on an Access database and and external Oracle database.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Further Reading:
Microsoft Press' book "Advanced Visual Basic 5" has an entire chapter devoted to converting existing versions of VB. It details the pros and cons, the whats and whys. If you have the current version of the MSDN, the full book is on the Library disc.
Thise excerpt from the book might also prove useful. For formatting purposes, I have included it as HTML.
zsi
========================== ========== ==========
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" Content="text-html; charset=Windows-1252">
<title>Summary of Changes from a Previous Version of Visual Basic to Visual Basic 5</title>
<style>@import url(stylesheets/msdn_ie4.c ss);</styl e>
<link disabled rel="stylesheet" href="stylesheets/msdn_ie3 .css"></HE AD>
<BODY BGCOLOR=#FFFFFF TEXT=#000000>
<FONT FACE="Verdana,Arial,Helvet ica" SIZE="2"><form name=x><object name=iv classid="clsid:9c2ac687-ce ef-11cf-96 d9-00a0c90 3b016">
</object></form>
<h1><a name="summaryofchangesfrom previousve rsionofvis ualbasicto visualbasi c5"></a>Su mmary of Changes from a Previous Version of Visual Basic to Visual Basic 5</h1>
<p>
The following table shows the changes you need to consider when you convert from a previous version of Visual Basic to Visual Basic 5.</p>
<table border=1 cellpadding=5 cols=4 frame=below rules=rows>
<tr valign=top>
<td class=blue width=148><b>Possible Pitfall</b></td>
<td class=blue width=148><b>Visual Basic 3 </b></td>
<td class=blue width=148><b>16-Bit Visual Basic 4</b></td>
<td class=blue width=148><b>32-Bit Visual Basic 4</b></td>
</tr>
<tr valign=top>
<td width=148>DAO</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
</tr>
<tr valign=top>
<td width=148>Windows 3.<i>x</i> APIs no longer available</td>
<td width=148>Unchanged</td>
<td width=148>Unchanged</td>
<td width=148>Changed</td>
</tr>
<tr valign=top>
<td width=148>Shell changes</td>
<td width=148>If moving from Windows 3.<i>x</i> to Windows 95 or Windows NT 4</td>
<td width=148>If moving from Windows 3.<i>x</i> Windows 95 or Windows NT 4</td>
<td width=148>If moving from Windows 3.<i>x</i> to Windows 95 or Windows NT 4</td>
</tr>
<tr valign=top>
<td width=148>New ODBC API library</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
<td width=148>Unchanged</td>
</tr>
</table><br>
<h1></h1>
</BODY>
</HTML>
Microsoft Press' book "Advanced Visual Basic 5" has an entire chapter devoted to converting existing versions of VB. It details the pros and cons, the whats and whys. If you have the current version of the MSDN, the full book is on the Library disc.
Thise excerpt from the book might also prove useful. For formatting purposes, I have included it as HTML.
zsi
==========================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" Content="text-html; charset=Windows-1252">
<title>Summary of Changes from a Previous Version of Visual Basic to Visual Basic 5</title>
<style>@import url(stylesheets/msdn_ie4.c
<link disabled rel="stylesheet" href="stylesheets/msdn_ie3
<BODY BGCOLOR=#FFFFFF TEXT=#000000>
<FONT FACE="Verdana,Arial,Helvet
</object></form>
<h1><a name="summaryofchangesfrom
<p>
The following table shows the changes you need to consider when you convert from a previous version of Visual Basic to Visual Basic 5.</p>
<table border=1 cellpadding=5 cols=4 frame=below rules=rows>
<tr valign=top>
<td class=blue width=148><b>Possible Pitfall</b></td>
<td class=blue width=148><b>Visual Basic 3 </b></td>
<td class=blue width=148><b>16-Bit Visual Basic 4</b></td>
<td class=blue width=148><b>32-Bit Visual Basic 4</b></td>
</tr>
<tr valign=top>
<td width=148>DAO</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
</tr>
<tr valign=top>
<td width=148>Windows 3.<i>x</i> APIs no longer available</td>
<td width=148>Unchanged</td>
<td width=148>Unchanged</td>
<td width=148>Changed</td>
</tr>
<tr valign=top>
<td width=148>Shell changes</td>
<td width=148>If moving from Windows 3.<i>x</i> to Windows 95 or Windows NT 4</td>
<td width=148>If moving from Windows 3.<i>x</i> Windows 95 or Windows NT 4</td>
<td width=148>If moving from Windows 3.<i>x</i> to Windows 95 or Windows NT 4</td>
</tr>
<tr valign=top>
<td width=148>New ODBC API library</td>
<td width=148>Changed</td>
<td width=148>Changed</td>
<td width=148>Unchanged</td>
</tr>
</table><br>
<h1></h1>
</BODY>
</HTML>
The book also makes reference to a VB3 to VB5 migration utility. As I only have an electronic version of the book, I do not not if this is included or if it is a separate utility. However, It is supposed to automatically convert API declarations and generate reports on other VB3-related issues.
zsi
zsi
ASKER
Thanks for you helpful answer......how do I read the html script???
ASKER
Thanks for your helpful answer......how do I read the html script???
Copy the HTML script into Notepad and save the file to a temporary directory. Name it something like "Conversion.htm". Then, load the page in to your browser of choice.
The biggest issue I've seen (and dealt with) is having ocx versions of the vbx's.