vfp or sql server

[dawg]

Our company is currently using vfp 5.0. We are looking to grow.  We were wondering if vfp would be able to keep up speed and dependability as we grow, or should we go to sql server?  Any tips would be appreciated.

 

[foxdev]

I've been using Fox since '87, and use it exclusively for client-side development.&nbsp;&nbsp;I've been using SQL Server for a couple of years.<br><br>If I was tasked with developing a reliable, scalable, and flexible system, I believe this is the best combo:<br><br>&nbsp;&nbsp;&nbsp;&nbsp;VFP client<br>&nbsp;&nbsp;&nbsp;&nbsp;SQL Server database<br><br><b>Reliability:</b> the DBF format is famous for data corruption.&nbsp;&nbsp;Its gotten better, but remains a problem.<br><br><b>Scalability:</b> I've used SQLS7 on a 100Gb database, with the largest table holding 270 million records.&nbsp;&nbsp;All this on a $75K machine.<br><br><b>Flexibility:</b> Somewhat of a toss-up; both can be tied to Web pages fairly easily, but SQLS can be accessed directly via TCP/IP from anywhere.<br><br>I think the combination of VFP/SQLS plays well to the strengths of both products.<br><br>I would still use the native DBF though for &quot;shrink wrapped&quot; mail-away type applications. <p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br>

 

[JDurbin]

Besides what Robert said if security is an issue you really have no choice but go with a data server like SQL Server.&nbsp;&nbsp;There is a 'desktop' version of it which I know nothing about and runs on Win98 I think but generally going with SQL Server means you will need to go with NT Server or Win 2K.&nbsp;&nbsp;If you post more specifics like securtiy, budget, scalability needs, etc you may find out more helpful info to help you decide.&nbsp;&nbsp;HTH <p>John Durbin<br><a href=mailto: john@johndurbin.com> john@johndurbin.com</a><br><a href=

http://www.johndurbin.com>

</a><br>ICQ #9466492<br>
ICQ VFP ActiveList #73897253

 

[foxdev]

Excellent point, Jon; I made a grave mistake not mentioning security, and security is not to be taken lightly, even in a closed environment.<br><br>As we all know, VFP and the DBF format provide absolutely no built-in security mechanisms on any level.&nbsp;&nbsp;No matter how bullet-proof we make our VFP app's security, anyone with access to the raw DBFs can read them.&nbsp;&nbsp;We can introduce encryption, but that greatly increases the complexity and negatively affects the performance of the application.<br><br>Database servers have excellent security built-in. <p>Robert Bradley<br><a href=mailto: > </a><br><a href=

http://www.foxdev.com/>FoxDev

- Visual FoxPro Development</a><br>

 

[Xaplytz]

I think, thank because VFP5 and VFP6 work with SQL-Server
With SQL-Sever you have all the protection and securities that you had with
The main frame for example all the write procedures is running in the server if something happened in the work station the data will be OK but if we work just with a LAN, if something happened with the workstation that could corrupt the *.dbf in the LAN-server.

The only two inconvenient I found working with SQL-Server :

1o. You have to make the whole and detail design before you start, because change something in the middle of the road is a pain in the neck or when the program is running and you boss want some modification, even now with SQL-server 7 a lot of things become easier.

2o. Because SQL-server is other Sever running inside of one computer in your LAN usually the same NT-server, you have to hire or give training to someone to be the SA (system Administrator) for you SQL-server, so now you have two Administrator one for the NT and other for SQL.

Therefore I believe SQL-server is not for small business.

 

[foxdev]

Microsoft did a great job making SQLS7 self-tuning. That, plus the decent tools that come in the box, gives your average VFP'er at least a decent shot at being to set up and run a smallish-sized SQLS/VFP combo.