Edited by Derek Page 1 Page 2 Welcome to the world of Windows CE programming. You are probably already aware that the development environment is much like VB's on the surface. Windows NT 4 or 2000 is required, unless you are prepared to do your debugging on the unit itself. Arrays of forms or arrays of controls on your forms are not supported. Nor can you hover the mouse pointer over a variable in the code window and expect to see its current value.
All variables are Variants.
An even more serious blow. Static variables cannot be declared within your Subs and Functions, you'll have to declare Private variables in the code module instead. This means that you could distribute code with latent problems as serious as undeclared variables, and it would only become apparent when the user hit the offending statement during an unpredicted sequence of events. Which brings us to the next section - eVB's error handling capabilities. If VB's error handling is crude, eVB's must be prehistoric.