Hi John..

Stored procedures, in the classic sense, do not exist in VFP. Yes, VFP has something called a stored procedure. However, you cannot run them through the VFP ODBC Driver. That said, I would classify them as pseudo-stored procedures..

Now, if we are talking about SQL Server, Oracle, etc, then we are talking about the real deal. Why do they provide? SP's provide a layer between your application and the underlying data schema. SP's also provide an additional level of security. For example, you can provide a user with Exec rights to a stored proc without granting the user Select, Update, Insert, and Delete rights on the base table. SP's allow you to define granular and finite operations that can be performed on data.

If you rely on SP's for all of your data access, updates, and queries, your data-base schema can change without the need to recompile your application.

From a performance standpoint, SP's represent compiled code. You often get the best performance form SP's. However, you do lose some flexibility in that you get out of the realm of dynamically passed SQL from client to server. However, SP's represent the most secure and safest route to go. After all, what is to stop a user from issuing a Select * against a multi-million row table. SP's can enforce the use of parameters that limit the result set.

Finally, the use of SP's is considered a "best practice" when creating Client/Server applications. In short, SP's are the way to go. And, when you compare these capabilities to VFP's version of SP's, you quickly realize that what VFP has does not come close to what SP's "really" are....



>Hi,
> What is the main reasons of using stored procedure?
> What functions that usually wrote as stored procedure?
> How to call stored procedure (VFP / SQL database)?
>
>
>Thankl you