SQL vs. VFP (for beginners) 4

[pt777]

I've programmed and re-programmed in VFP, VBS script, Html, and COM for about 12 years and haven't yet understood SQL concepts per se. I haven't yet tried the Upscale Wizard for converting VFP to SQL: Some basic questions:

Is upscaling (using the Wizard) to SQL a seemless operation with complex VFP Apps, Exes, tables, reports, COM, and all ?

What does SQL do that VFP can't do (and/or vice versa)? That is to say, is SQL more efficient and/or desireable in most cases ?

After compiling in VFP (repeatedly), is it desireable to upscale to SQL everytime ?

I would appreciate (in advance) any level of feedback in this area from any of you.

 

[Mike Gagnon]

pt777

Is upscaling (using the Wizard) to SQL a seemless operation with complex VFP Apps, Exes, tables, reports, COM, and all ?

You do understand that upsizing only changes your data and not your executable. So once you have upsized your data to a Microsoft SQL server, you can still "retain" your VFP interface and communicate with your data with views (or ODBC connection).

After compiling in VFP (repeatedly), is it desireable to upscale to SQL everytime ?

No, since it only deals with the data portion of your application.

What does SQL do that VFP can't do (and/or vice versa)? That is to say, is SQL more efficient and/or desireable in most cases ?

One of the advantages of moving your data to an SQL server is your are no longer restricted to the 2 gig limit per file.




Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[MarciaAkins]

Hello Pt777.

>> I haven't yet tried the Upscale Wizard for converting VFP to SQL: <<

I do not recommend using the upsizing wizard because it makes a lot of assumptions and bad decisions about how to move your data into SQL Server.

>> What does SQL do that VFP can't do (and/or vice versa)? That is to say, is SQL more efficient and/or desireable in most cases ? <<

In addition to what Mike said about the 2GB limit, there are other advantages to using SQL Server to store your data. One advantage is that it is much more secure than VFP tables. Another advantage is that you can use triggers to update the record that you are currently inserting (you can't do that in VFP).




Marcia G. Akins

http://www.TightlineComputers.com

 

[Mike Lewis]

Pt777,

I know this doesn't answer your question, but are you confusing SQL with Microsoft SQL Server. The first is a language which is supported by most database products, including VFP. The second is a particular back end database.

The upsizing wizard is concerned with migrating data from a VFP back-end to a SQL Server back end. However, it is not the only tool that does that job (and, as Marcia says, not necessarily the best one).

Perhaps you could clarify exactly what you want to achieve, and we can then advise on how best to go about it.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[pt777]

To Mike, Marcia, and Mike,
You've all enlightened this aspiring amateur much.
Thank you.

Truth is:
1) I am very ignorant with SQL server (as well as Oracle platforms and such) and don't understand much of what I've read on it. (Yes, I confuse it with our venerable SQL statements, too)
2) I have seen it 'behind' some (competitive) apps at medical meetings
3) ... wondered if it was actually a programming (high level) language or something worth dabbing into for medical apps.
4) ...Also, curious if it works 'better' as a server for wireless client-computers (per se).

(Like SOAP and many other recent VFP goodies ... that so often seem to defy my comprehension ... I am trying to get a feel for their cost-effectiveness in grand schemes of things, etc.)

 

[Mike Gagnon]

3) ... wondered if it was actually a programming (high level) language or something worth dabbing into for medical apps.

If you are familiar with VFP, there is much you need to learn to be able to "talk" to an SQL server, the interface can remain the, you just need to learn the "way" to communicate with the SQL database through such tools as ODBC.

...Also, curious if it works 'better' as a server for wireless client-computers (per se).

Depends on the budget of your client.



Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[Mike Lewis]

Pt777,

I wonder if perhaps you are starting at the wrong end. Instead of asking how to use SQL Server, maybe you should be focusing on what specific problems you've got that SQL Server might be able to solve.

If you haven't got any compelling reason to move to SQL Server, my advice would be to leave it alone. Migrating to any new back end will be a lot of work and a lot of learning. Don't do it unless it will bring you tangible benefits.

That said, SQL Server does have many advantages: better performance (through reduced network traffic), larger tables, better security, on-line backups, etc. But only you can decide if those benefits justify the cost and effort.

Mike


Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[pt777]

Again Mike and Mike,

Your thoughtful responses are noted and appreciated. At present I won't take the SQL plunge for tinkering's sake. The saying: "much knowledge brings much weariness ... and of writing books there is no end" ... comes to mind.

Also, I'd prefer to leave SQL server alone as well on artistic grounds, seeing that VFP (and COM) seem to cover many mediums, already.

Philip

 

[JRB-Bldr]

If you want to use the VFP envvironment for application development it is best to get a good foundation built within the "native" VFP databases & tables.

You will be able to learn the use of VFP's SQL commands and get comfortable with them as well as all of the other VFP capabilities of which there are many.

SQL Server has a number of advantages if/when you need either an "intelligent" back-end and/or you need the larger data tables capacity mentioned above.

BUT note that SQL Server comes with a $$$ pricetag that is justifiable in some circumstances and not in others.

If you get to the point where you want to "take the SQL Server plunge for tinkering's sake" you might want to consider the MSDE version of SQL Server (Version 7). It is free and it is considered by many to be the "beginners" SQL Server although it is pretty well fully functional.

Also in regard to: "I have seen it [SQL Server] 'behind' some (competitive) apps at medical meetings". Quite a few applications are built using the VB + SQL Server approach. That is largely due to needing an intelligent back-end such as SQL Server (or Oracle, etc.) to overcome the data manipulation/processing shortcomings of VB (a problem not usually found with VFP).

Good Luck,
JRB-Bldr

 

[pt777]

Thanks JRB for your empathetic insight and increasing my confidence in VFP per se.

Philip

 

[stable]

Hi Mike, Marcia and Mike,

I was interested to read your thoughts on the upsizing wizard.

I am currently redeveloping an application that currently uses a Visual FoxPro database. The new system will be MS SQL Server database with MS Access Project front end. Can you tell me how I can migrate the data to the MS SQL database? The current data is held in .dbf and .cdx files.

Any help would be much appreciated.
Stables

 

[MarciaAkins]

Hi Stable.

>> The new system will be MS SQL Server database with MS Access Project front end. <<

Just curious here. Why not keep a Visual FoxPro front end? If you are changing front end tools why are you moving to Access instead of .NET?

>> Can you tell me how I can migrate the data to the MS SQL database? <<

Presumably, if the application is being re-written, the data structures need to be modified as well. You will need to write a VFP program to take massage the VFP data and move it into the new structures.



Marcia G. Akins

http://www.TightlineComputers.com

 

[Mike Lewis]

Stable,

I agree with all of Marcia's points. See also our earlier comments on the upsizing wizard. In general, I prefer to use my own upsizing code, rather than relying on the wizard, for the reasons stated earlier. Those reasons still hold, regardless of whether you use VFP or Access as the front end.

Mike


Mike Lewis
Edinburgh, Scotland

My Visual Foxpro web site:

http://www.ml-consult.demon.co.uk

My Crystal Reports web site:

http://www.ml-crystal.com

 

[pt777]

I think I'm sticking with VFP based on your input,

Thanks,

Philip