jaymz69
asked on
Books/Links on VFP to SQL Server
We have new senior management and they want to go away from the VFP and do SQL Server 2008
So I am converting my VFP programs to SQL Server
But trying to figure out how SQL Server will do what VFP does for me
Date Variables, parameters, and so on....
Anyone knows of a reference book or link on this subject?
Thanks
So I am converting my VFP programs to SQL Server
But trying to figure out how SQL Server will do what VFP does for me
Date Variables, parameters, and so on....
Anyone knows of a reference book or link on this subject?
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You might need to have an 'education' session with the individual(s) who wants you to change to SQL Server.
You can 'educate' them that SQL Server, as a SERVER, is a repository for data, not an application builder. Think of it as a responder to an application.
SQL Server can execute its own T-SQL code to accumulate/insert/update data in its data tables.
And through things like SSI and stored procedures within SQL Server, you 'automate' certain operations, but they typically use 'fixed' parameters or parameters which are passed to them via an 'outside' application.
If you have an APPLICATION today (VFP?) which allows users to make dynamic entries and manipulates data from those pieces of dynamically entered data, SQL Server can work with the data, but it cannot, by itself, get the data into itself. It will take an APPLICATION to do that.
Good Luck
You can 'educate' them that SQL Server, as a SERVER, is a repository for data, not an application builder. Think of it as a responder to an application.
SQL Server can execute its own T-SQL code to accumulate/insert/update data in its data tables.
And through things like SSI and stored procedures within SQL Server, you 'automate' certain operations, but they typically use 'fixed' parameters or parameters which are passed to them via an 'outside' application.
If you have an APPLICATION today (VFP?) which allows users to make dynamic entries and manipulates data from those pieces of dynamically entered data, SQL Server can work with the data, but it cannot, by itself, get the data into itself. It will take an APPLICATION to do that.
Good Luck
ASKER
They think SQL Server can do everything VFP can do for the queries and reports. Perhaps it can? He suggests all the VFP reoprting I have running will need to convert toe SQL Server, maybe TSQL...?
I was telling him about how in VFP I can take data quickly now with SQLEXEC() and manipulate the data, variables, store DBF for later data compareson.
Only time can tell? I