>You had mentioned in the VFP forum some difficulties using VB with the Pocket PC. What were your findings?

eVB is not based on the same engine as VB for Win32. eVB is really like VBScript, meaning:

- You can't create ActiveX controls with eVB, you must use eVC for that
- Only one data type is supported, variant, which is slow to access and take a lot of memory
- You can't unload a form once it is instanciated
- Only one .BAS module can be created
- Only On Error Resume Next is supported for error trapping (ouch!)
- Language errors are checked only at runtime. You better make sure that every line of code is executed at least once before you ship your app...
- No support for API calls. If you want to call an API, you need to create an ActiveX that will do it for you (which of course can only be built with eVC...)
- You again need an ActiveX control if you want to provide a help system to your users
- debug.print doesn't work
- You are limited to ADO CE to access the database, which is slow on CE
- You can't create a COM in eVB, only with eVC
- Slow
- Bug: Left() doesn't work in a form
- Bug: Cursors won't work in a textbox
- Bug: If you use a frame control to group related controls together, you lose the Click() and Change() events for combo boxes and text boxes
- Bug WinSock: The connection is closed before the DataArrival() event fires
- Bug WinSock: You cannot access another machine over an Ethernet connection
- Bug WinSock: Return the correct data once in every 3 to 5 attempts. Doesn't generate any kind of runtime errors
- Bug WinSock: Setting RemoteHost to an IP address doesn't work. Only URL address is supported

Note: I did not test every items mentionned above. Most of the items come from Larry Roof Professional Visual Basic Windows CE Programming book (WROX 1-861001-62-2).

eVC is better, but isn't perfect either. Apart from being harder to learn and use than eVB, some class doesn't work has documented, like the CSrollView class that doesn't refresh correctly the screen.

Whatever the tool you choose to build your app, you need to learn all the specifics of the Win CE platform. You don't develop your app in the same way on CE than on the desktop. Apart from the smaller screen size, not all the functionalities of the desktop API are available, you can have only one instance of a program running, you can't manipulate other app via OLE, MDI forms are not supported, everything is in memory, an application can be asked to shut down by the OS if the memory is running low, etc. There are many new situations that you need to adapt to.

HTH