>Thanks again Al. I'm still concerned because the FoxPro program will get about 1000 records per week with 6-10 users. Worse yet the client has many other programs running on the same workstations that will be running the Foxpro program. If something goes wrong there will be Hell to pay.

One of the apps in the environment I mentioned earlier is VFP5. It's been running about 15 years and has accumulated just under 1 million rows in the main transactions table. That's an average of about 1,200 rows per week. Peak is actually much higher because their business is seasonal and most of the rows are input from September to January.

My understanding is VFP9 is more reliable than VFP5.

As I've remarked many times before, a multi-user VFP app is a quick way to point out any weaknesses in site infrastructure. My recommendations for multi-user native VFP table-based apps:

- Reliable, properly configured server-grade server preferably from a tier 1 vendor
- Reliable, properly configured workstations
- UPS power for server, optional for workstations
- Wired Ethernet network connections, gigabit or better. Good quality switchgear and cabling
- No wireless networking allowed for multi-user VFP apps
- Properly configured networking - DNS, router/gateway, firewalls (hardware/software) etc.
- A Windows domain and domain controller make life easier
- Solid, tested, scheduled and monitored server backup
- Malware-free workstations. Antivirus products (workstations and server) should be configured so real-time scanning does not scan VFP data tables or workstation VFP temp file folders, or that it excludes all VFP data and temp file types
- Workstations run only business software. No iTunes, streaming radio, FaceBook etc.
- Corporate-grade tech support available for first-level support, and installation of your app (if you're not doing that yourself)
- SMB2 registry settings on all clients, as discussed earlier

Personally, I'd be up-front with the potential client and tell him or her they need to meet all of the above to ensure reliable operation. If they do you have little or nothing to worry about. On the other hand, if it's a network of 10 motley no-name workstations running peer-to-peer with 1 designated as the "server", and connected via WiFi, they're probably not a good candidate.