Re: Stored procedures vs. views for filling record sources
- From: "James Goodman" <james@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 20 Oct 2005 20:20:37 +0100
That depends on your requirements.
A stored procedure is generally more secure, and will perform better because
of caching etc, but a view can be selected from (e.g. SELECT SomeCol FROM
SomeView). You can also use UDF's which are cached like sp's, but can be
selected from.
Views do not support parameters, sp's and UDFs do.
Depening on requirements, I often use Views for updateable recordsets
because they are normally easier to bind and modify etc, but for read-only
recordsets I normally try to use SP's.
Outside of Access, where updates/inserts etc have to be written I always
prefer to use SP's.
"Andy G" <ajgould@xxxxxxxxxxx> wrote in message
news:OuxqTJO1FHA.560@xxxxxxxxxxxxxxxxxxxxxxx
> Should I use a stored procedure or a view when filling a record source in
> an .adp?
>
>
>
.
- Follow-Ups:
- Re: Stored procedures vs. views for filling record sources
- From: aaron.kempf@xxxxxxxxx
- Re: Stored procedures vs. views for filling record sources
- References:
- Prev by Date: Table and Query Descriptions in ADP
- Next by Date: Re: Export data from ADP file
- Previous by thread: Stored procedures vs. views for filling record sources
- Next by thread: Re: Stored procedures vs. views for filling record sources
- Index(es):
Relevant Pages
|
Loading