Many additional differences between eVB and VB6 are either self-explanatory or don't warrant an entire paragraph to describe. The following is a list of those differences:
-
Some project files have changed extensions. Forms in eVB end in .ebf; project files end in .ebp.
-
eVB controls support only 256-color graphics. Trying to load a PictureBox with a 32,000 color image causes an ambiguous error that's difficult to debug, so be sure that all picture files have a color depth of 256 colors or less.
-
You can't write custom add-ins for eVB, nor are any supplied from Microsoft.
-
Because eVB is interpreted, AddressOf isn't supported. Similarly, you can't use VarPtr or StrPtr to retrieve the address of a variable.
-
SQL in ADOCE doesn't support the UPDATE command. You must either use DELETE and INSERT or create an ADOCE recordset and use its Update method.
-
The SQL INSERT command can take only a VALUES list. It can't contain subqueries.
-
You can't JOIN more than four tables.
-
You can't have ambiguous column names in a join (i.e. the same column name in two tables).
-
The only JOIN supported is the INNER JOIN.
-
Only JOINs on equal fields are permitted.
-
The Format() function isn't supported. Several new formatting procedures have been added: FormatDateTime, FormatPercent, FormatNumber, and FormatCurrency. Any other type of formatting requires you to roll your own procedure.
-
The Load and Unload commands (that is, Load Form1) are unsupported. Be sure to clean up control modifications on loaded forms such as where you've added to collections (TreeView nodes, ListView items, and so on) if the form is to be conceptually loaded again.
-
The conditional compiling directives (#If...Then...#Else, #Const) are unsupported.
-
The Shell() command is unsupported. Use the CreateProcess API instead (see Chapter 9).
-
Static variables are unsupported.
-
The Left() string function is unavailable in a form's code page because eVB interprets it to be the form's Left property. Left() works fine in a module.
-
DoEvents isn't supported. A workaround is provided in Chapter 9.
-
The SaveSetting and GetSetting Registry functions aren't supported. See Chapter 9 for implementations for Windows CE.
-
Custom properties (that is, Property Set and Property Get) aren't supported. Instead, twin methods must be used. See Chapter 3 for an example.
-
The eVB ListBox doesn't support the CheckBox style.
-
eVB doesn't support the Date, Time, or Timer statements. See Chapter 9's examples for GetLocalTime and GetTickCount.
-
Option Base and Option Type aren't supported.
-
Arrays can't have a lower bound other than zero.
-
Collections aren't supported.
-
The ! operator (as in objRs!Field1) is unsupported.
-
GoSub is unsupported.
-
Line numbering isn't allowed.
-
End is unsupported. Instead, use App.End.
-
The following conversion functions are invalid: Str, Val, Cvar, and CVDate.
-
eVB has no Debug object, so Debug.Print and Debug.Assert are invalid.
-
The TypeOf function is unsupported.
-
Select statements using Is or To are invalid (for example, Case obj Is Nothing, Case 1 To 5).
-
Beep() is unsupported. See Chapter 9 for the PlaySound API.
-
All string commands containing the $ character (Left$, Right$) are unsupported.
-
LSet and RSet are unsupported.
-
The Like operator isn't supported.
Caution
Just because something comes up in IntelliSense does not mean eVB supports it! The eVB IDE was very likely derived from the VB6 IDE, and therefore some VB6 functions will show up in IntelliSense. When in doubt, check the eMbedded Visual Tools help files. As a general rule, if it isn't in the help files as an eVB function, it isn't supported.
