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
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.