I'm actually in the process of doing the same thing.  We have a legacy
FoxPro application and all of the data is currently in VFP free tables.
I am going to start moving the data to SQL Server.  I have chosen the
approach of using SQL stored procs with T-SQL commands to do all
querying, updating, etc...  For what you are doing, I think stored procs
are definitely the way to go.

Thanks,
 
Nick Cipollina
 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Michael Babcock
Sent: Thursday, July 27, 2006 2:58 PM
To: [EMAIL PROTECTED]
Subject: [NF] Views in SQL Server

I'm creating a new app that uses brand new SQL Server tables.  This app 
is currently VFP for the UI but it'll be going DotNet in the future 
sometime, and I'd like to design for that migration now rather than 
later since this is a new app.  I like to use Stored Procs for the 
benefit of re-use, and had started writing a simple stored proc to 
return the dataset desired (like a parameterized view in VFP). 

I had heard something long ago that views in SQL Server (2000) didn't 
function the same as views in VFP.  I recall something about a 
performance issue?  Come to think of it, it wasn't SQL Server where I 
was told this---it was on an Oracle 9i system.  They didn't like to use 
views for some performance concern (and that came from the DBA, iirc).

For those who integrate VFP with SQL Server...would you set up a SQL 
Server view and then have a stored proc that returned the view, or would

you just write the SQL Select code into the stored proc and return 
that?  I'm unfamiliar with how parameterized views work in SQL 
Server...I'm hoping it's as easy as in Fox, but I doubt it will be.  ;-)

tia,
--Michael



[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to