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
_______________________________________________
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.
