>If I develop a commercial system in VFP (and I realize SBT has one already) I am going to have to explain to my resellers why it isn't written in Access (since that is what they have gotten from us before) and how they can still write add-on's for it even though they don't know VFP.

Jon that should be easy to explain,
VFP is apart of Visual Studio, therefore it is higher end software development tool. Access is apart of Microsoft Office, it's more of an end user tool and therefore not as robust (as you've seen with your product in a network environment). Also, you got the native database engine in VFP in your favor. So when compared to VB (or other comparable VS tool) your not giving up the internal database handling your use to with Access and you won't have to go thru an extra layer for add-ons (VB or other will need to implement additional controls to simulate native db engine). Plus, since you say your clients aren't quite ready for client server, it sounds as if VFP is a very practical next step as opposed to the common trend for SQL Server + VB frontend. HTH