Hi Jim,

I've done several VFP apps that have needed to run over wireless and I've found that it's really takes a different mindset. You have to develop with the knowlege that your connection to the network (and your backend data) can drop at any time.

Here are a few things that I try to do when developing for wireless.

Use UNC pathing to data. It survives even if a drive mapping doesn't.
When you're polling data, put your data access routines into a try/catch.
Don't leave tables or databases open for long periods of time if you can help it.

Here's a small example.

FUNCTION PollSomeData
*
DO WHILE ! llExit
  TRY
    USE MyTable shared 
    DO SomeProcessing  &&--Put TRY/CATCHes for data accces w/in here too.
    USE IN MyTable
    llExit = .T.
  CATCH TO oErr
    *--Warn the user that the wireless connection has dropped and ask them to 
    *--retry.  Or if unattended, rety automatically in a few seconds.
    *--Set llExit accordingly.
  ENDTRY  
ENDDO

Hope that helps. It's definitely helped me lessen the amount of trouble calls.

-Matt