Alan,
This is a good idea too, but will mean a lot of refactoring of existing code.One good approach is to place an encrypted ini file on a server at each customer, containing the site's individual connection string with login details etc. At the start of your app, unencrypt the file and use it to create a public variable or persistent property with the handle. Then use gofish to find all your USE commands and add CONNSTRING m.pHandle. Do that for local views as well- Connstring is ignored if the views are local and if you ever convert them to remote views, it'll keep working. Now you can copy your app files to any pc in the facility and it'll work, as long as the proper odbc drivers are available.
A certain hospital not too far from you uses this exact system, allowing them to use a VFP app on ? 1,000 PCs with no contention or other scaling issues that are so often reported for VFP. ;-)
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
