>We currently have a couple of clients looking to expand current software solutions to incorporate Pocket PC devices. The include restaurant and remote order taking/delivery type applications. We are looking at what the best approach is, and I am wondering if anybody has good suggestions. We would like to be able to include networking functions for sending orders/transactions without a hotsync as well as the ability to print invoices or tickets to networked priters without going through a PC.

Look for devices that have a built in wireless network card.

>I am looking for suggestions for:
>
>- Best Pocket PC hardware to use for functionality/flexibility/price. Is there any particular unit that lends itself better to development? We will want to incorporate barcode scanning, any good/bad experiences with different barcode option (pc/card, cradle, etc.)?

That depends on the needs. If you think that the users may drop the units, consider a ruggedized unit like Hand Held Product Dolphin 7400 (http://www.hhp.com/hhp/products/product.tpl?prodsku=8057804795367) or Intermec 700 (http://home.intermec.com/eprise/main/Intermec/Content/Products/Products_ShowDetail?section=Products&Product=CMPTR700&Category=CMPTR&Family=CMPTR2).

>- Best development tools. My employer is very big on sticking with the Microsoft platform so we are thinking about VB.net. Of course we have to integrate the data with our existing VFP application.

To use VB.NET, you need a device that come with Pocket PC.NET. Older versions of Pocket PC or Windows CE won't allow you to use .NET. You will also have to consider that the .NET CLR for PocketPC.NET is still in beta...

Otherwise, you can use eMbbedded Visual Tools 3.0 that can be ordered from Microsoft for the cost of shipping.

eVT offer two languages: eVB and eVC. I have to warn you to be carefull if you want to use eVB. It is not the desktop equivalent. It really is VBScript. It have a lot of limitations, including:

You need the Pocket PC version of all ActiveX that you will use (if available). Don't count on using the same ActiveX that you use on the desktop

Only one data type available: variant (yuk!)

There are no End or Unload statements

You are limited to a single .BAS file

No OLE support

No MDI forms support

You cannot create a class module

Cannot unload forms. You can only hide them

Only one error handling mode: On Error Resume Next (!)

Language errors are handled at runtime. That's right, to know if you have made a typo, you have to execute the code...

No API calls

No help support

So, unless your application is really simple, I strongly suggest that you use eVC instead.

There is no drivers for .DBF tables in Pocket PC. So you will need to find a way to synchronize you data between the device and your VFP application. These tools can be used on Pocket PC:

SQL Server CE (can be used for free if you have a license for the desktop version of SQL Server)

Pocket PC internal database (not available from eVB, since you access it by API calls). Really slow with more than about 5K records and is not relational. 2 records can contain completly different fields

Access

File

>- Resources to get started. Is there a good book or some good websites? Of course this is probably tied to the development tool used.

http://www.amazon.com/exec/obidos/ASIN/0130255920/qid=1036002361/sr=2-2/ref=sr_2_2/103-0940491-1567064
http://www.amazon.com/exec/obidos/tg/detail/-/0201616424/ref=pd_sim_books_1/103-0940491-1567064?v=glance
http://www.pocketpcdn.com/

HTH