Mark,
For a desktop app with say 1-5 screens and a small database there are two ways to go:

Desktop Syncs:

Visual CE - http://www.syware.com/prodlib/win_ce/vce/vce.htm
Upside - Fast(weekend to get an app up), easy syntax, sync is done for you
Downside - Lanquage is not very flexible but if you build to their specs no problem

MSFT Visual Basic Embedded
Upside - Powerful language, supports Active X, Fast, ADO CE enabled
Downside - Much longer learning curve,Buggy - Memory Leaks, have to build your sync - not a big deal if you put your VFP data (remote view) in a Access MDB and then sync this to the Pocket PC CDB

Wireless try this application:

Here’s the URL: http://www.wavelink.com/Wavelink/WirelessApplications/Studio/index.asp

To summarize, Wavelink Studio includes 3 pieces of software: 1) A Server; 2) A handheld specific client; and 3) Libraries that talk to the client via the server. All 3 appear to be very well written and can be running in less than a day. If you want to demo the software, it is available for download and you’ll receive license information via the email address you register with. You must enter the license information in the server configuration before any connections are allowed.


Good luck with whatever you choose. I recommend using Visual CE for your first app. This is the small investment, big payback type of choice. Consider this your training wheels app for getting use to the environment and its limitations, and to discover what your users consider important in a handheld. Then, after this beta period, you can fine tune the model in say VBE, Wavelink, or .NET and position the product for the Enterprise with MSFT Compact SQL.

Jim





>James,
>could you go into further detail please? we want to develop a small app for the windows ce device but neet to know the best way to do it, ie language to use etc.
>Cheers
>~M