Daniel,

Thanks so much for the response. I guess then, as long as my table sizes can be handled by VFP and security isn't an issue I could just stick with using VFP all by itself even for my larger clients?


>The decision on whether to move to a different back end really isn't based on how many computers will work with a system. SQL Server offers the ability to work with much larger table sizes than VFP supports, much better security, and the ability to work with the front-end of your choice (which may be a big plus if you are thinking about web access to the data). The penalties can be speed (client/server doesn't mean faster), cost (more hardware, more software) and of course the time you'll need to spend converting your app.
>
>Be aware too that your smaller clients may not WANT to move to a different backend, although SQL Server 7.0 will run on a Windows '95 or higher system. It may be a simple matter of cost for them.
>
>>I have a large client base using my dos accounting software package. I have been rewriting this package using VFP for the last couple of years. I have stores using my software that range to having 1 stand alone machine to stores that have 40 computers on a Novell network to Stores using citrix across a wan of 8 stores consisting of close to 100 computers.
>>
>>Right now I have been developing my package with just the base VFP tables.
>>
>>Will this work for all of my clients? Should I be looking into some kind of backend server? If so is there a general rule of thumb of how many computers will work with just the VFP tables as opposed to a backend server?
>>
>>Thank you very much,
>>Paul Acton