Does a VFP app correctly runs on a wifi network?

Exactly. Not good choice in some cases. Why?

Speed could be OK but WiFi is not stable network, the signal is fluctuating with many interferences raising to possible connection interruptions which may cause 11xx errors when DBFs are on a shared drive accessed via WiFi network. And to recover from 11xx error is often not easy and harmful for data writes...

Safer option is to connect to a Remote Desktop via WiFi and run the VFP application in Remote session which means local (fast and reliable) access to data in fact. Another option is to connect to SQL Server via WiFi and then use local FoxPro cursors in your application.

When you decide to use WiFi access then remember the app code and run-time modules and possible read only data should reside on the local computer (not applicable for RDS) to minimize the network traffic. If you place data on the SQL Server then you should also code for minimal network traffic because this is still the bottle neck for VFP apps.

OTOH, WiFi in the 5 GHz range seems to be much more stable and faster than the older 2.4 GHz band. I did not try VFP app in the 5 Ghz WiFi network yet and it would be worth to test it. But the basic rule is still valid: The WiFi reliability declines with the distance from Access Point. I am always preferring the wire (or optics).

Hi Pcelba.

Thank you for so complete reply.

Could you better elucidate:

Safer option is to connect to a Remote Desktop via WiFi and run the VFP application in Remote session which means local (fast and reliable) access to data in fact.

Did you mean by this that the Remote Desktop will hold the data (DBF/ CDX/...)  so it will be the "server" and the others (clients) will have just the data  tables  concerned to its own operation  plus (.exe/ .fll/ ...)  ?

Doing that way a wifi network could be working adequatelly?

So, if I well understood, is it like a TeamViewer operation?

Just this is not very clear now

... More obvious is to create a copy of the application for each logged-in user as it also allows simple automatic updates.

What's the reason for that if the .exe used remains in remote desktop?

To have the application copy for each user on the server allows to update it when users are running the app. You may upgrade the app on the server folder which is used as the reference version. Users do not execute the app in this reference folder but just some small startup.EXE which compares the version in user folder against the server version, copies the new version to user folder if necessary, and executes it.

Perfect.

Just one thing I'm  not certain it's correct, Teamviewer doesn't allow more than one remote connection at the same time (non-commercial version).
When using  Windows Remote Desktop - I don't know if it's a matter of configuration, when a user enter in the user that entered before is knocked down.
(You suggested RDS licenses)
Could you clear?

TV is something like one desktop sharing or remote control whereas in RDS does each user have its own separate environment.

Thank you for so complete reply!