>Can this be true? No callbacks with VB anymore. We just got them. I use both languages for different tasks. For Data VFP can't be beat but for other things VB is best.

I may have mis-interpreted (or mis-recollected) the list from Karl's site (see original message). Here's the list from his site.

VarPtr is not supported.
StrPtr is not supported.
ObjPtr is not supported.
As Any is not supported for API Declares.
Use of ByVal/ByRef directly within API calls is not supported.
Arrays may not have a lower bound other than zero.
Option Base is not supported.
Variants are not supported. Object is now the default data type.
Currency is not supported.
Dates are not stored internally as Double values.
Longs are not 32-bits; they are 64-bits.
Integers are not 16-bits; they are 32-bits.
True is not -1, but is 1 instead.
The Imp and Eqv operators are not supported.
Fixed-length Strings are not supported.
DefInt, DefLong, et al., are not supported.
Dim may not always create procedure-level variables.
Redim will not create arrays not already declared.
Local variables are not necessarily visible throughout a procedure.
Null is not supported.
Empty is not supported.
IsMissing is not supported.
Terminate will not fire when an object's last reference is released.
Object finalization code will not execute in a predictable order.
Public object variables are not safe from alteration when passed as parameters.
Can not expose Property procedures with mixed visibility (Friend Set/Public Get).
Procedure parameters are not by default passed ByRef anymore.
ParamArray arguments are not passed ByRef anymore.
Implements is not implemented the same, so must be rewritten.
Static is not supported as a procedure level modifier.
Use of As New does not force auto-reinstantiation when an object is released.
Parenthesis are not optional when calling procedures.
Set is not supported for object assignment.
Parameterless default properties are not supported.
Default values for Optional parameters are not optional.
Code is not compiled to native, thus making decompilation much easier.
Resource files have changed format and old ones are not supported.
LSet is not supported.
UDTs are not Types, but are called Structures instead.
UDTs are not by default contiguous blocks of memory, but are objects.
Enums will not be recognized unless fully-qualified.
While/Wend loops are not supported.
GoSub/Return is not supported.
On/GoTo is not supported.
On/GoSub is not supported.
And, Or, XOr, and Not are not bitwise operators.
Comparison operators are not evaluated before logical operators.
Control arrays are not supported.
Windowless controls are not supported.
Image controls are not supported.
Shape controls are not supported.
Line controls are not supported.
OLE Container controls are not supported.
Label controls will not have a Caption property.
The Tag property is not supported.
Setting a Timer control's Interval to 0 does not disable it.
Top-level menus may not be used as context menus.
Old forms using vbPixels for Scalemode will not upgrade correctly.
DDE is not supported.
Circle is not supported.
Cls is not supported.
Line is not supported.
PSet is not supported.
Point is not supported.
PrintForm is not supported.
The Name property for forms and controls is not exposed at runtime.
Print will not include a linefeed at the end of a line.
File I/O will not be compatible, at all, and must be rewritten.
Printer object methods are not automatically upgraded and must be rewritten.
Clipboard object methods are not automatically upgraded and must be rewritten.
Screen.MousePointer does not have a direct replacement.
Webclasses are not supported.
DHTML projects are not supported.
ActiveX Document projects are not supported.
The IDE Extensibility Model is not backwardly compatible.
The Immediate window will not work in Design mode.
Data binding with DAO is not supported.
Data binding with RDO is not supported.