I have been using VFP flat files for a while now and want to get into SQL interface. Just want to know whether it has a front end facility where one create forms and do programming chores like VFP.
I assume you are referring to Microsoft SQL Server? If so, it has several front end tools. The first two mentioned below should be available from your start menu (assuming you elected to install 'client tools' at install time):
- Enterprise Manager. A point-and-click interface, designed for administrators.
- Query Analyzer. Similar to VFP's command window; lets you enter commands for immediate execution.
- OSQL. A primitive command-line utility, useful if all else fails.
Note that none of these tools are designed for creating applications. SQL Server is not an application development tool. Most people use VFP, VB or something similar for development.
You cleared every doubt in my mind. I take it that the 'Client Tools' allows the user to run queries and make raw data input. I thought that it had some application development facility. Thanks very much. I know now what I am getting into.
Thanks. Actually, I am going to install a 120 day evaluation copy of SQL Server 7 this weekend to begin experimenting with VFP interfaces. I would love to know some of the differences between working with flat files .dbf and DB Servers.
Will I still be able to run the the following commands or do I have to copy the Server's data to my local machine in a .dbf before I can use it. Or, does my data comes in as a cursor which I can use. Then comes the question. I can't INDEX on a cursor. What about commands such as PACK. What are their relevance in a Client/server environment?
Working in SQL Server is quite different from VFP. There is no SEEK, SCAN, LOCATE, GO TOP, etc. Everything will be using SQL commands. Start thinking of working with sets of data instead of the entire table.
You can access the data in a couple of ways. 1) ODBC, which will return a VFP cursor. This can be done with SQL Pass Through (SPT), remote views, or CursorAdapter. 2) OLE DB, which will return a record set if used directly or a VFP cursor if used through the CursorAdapter.
You won't pack SQL Server...data is stored differently than VFP. No need to pack.
Instead of a trial version, why not get SQL Server 2000, Developer Edition for $50.
I recommend you read the VFP documentation on client/server and the VFP articles on at mdsn.com/library
I am not so rich as yet, very poor guy. Will purchase SQL 2000 after I have become comfortable with this new data access method. Your post was of great help. However, the VFP help on Client/server seem to be making assumptions that I don't match. I will try the articles you mentioned.
Craig has already given you some good advice. I would add that the design philosophy of a SQL Server-based application is somewhat different from one using a VFP back end. There are also many fundamental differences in the detail.
On the other hand, there are some substantial benefits in using SQL Server as a back end. Personally, I am very glad I took the effort to learn it; it has paid me back many times over.
If you are still at the experimenting and learning stage, my advice would be to install the 120-day eval, and to learn as much as you can during that time. There's a lot of information available to help you. By the time you have done that, you will be in a good position to judge whether you want to go further with it.
And don't forget, you can always come back here if you have any questions.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.