Jet MDB's support very simple stored procedures using
Jet or ODBC SQL and VB inbuilt functions.
When Jet MDB's are used with Access, you can also use
user defined functions built in VBA and stored in the
database.
But using Jet MDB's, you can't use Triggers or
Transact-SQL, the programming language of MS SQL Server.
Jet queries are procedures, and they are stored in the
database: they are stored procedures.
To many people, stored procedures aren't stored procedures
unless they say "procedure" at the top. Jet now has this
ability to store procedures with this magic word included.
The Access help files tell you how to create stored procedures
that have the word "procedure" at the top.
Access/Jet used to delete the redundant text if you put
"procedure" at the start of your stored SQL.
Today, the ability to use Declarative Referential Integrity
in SQL Server means that the most important demand for simple
stored procedures in SQL Server no longer exists. Today,
stored procedures in SQL Server are only used for complex
tasks, the kind of thing you would do in Access using a
VBA user defined function. That means that when SQL Server
people now talk about stored procedures, they are talking
about complex stored procedures, written in Transact-SQL.
The ability to create and store "procedures" in a Jet
MDB does not give you the ability to use Transact-SQL
or Triggers - the important features of Stored Procedures
in SQL Server.
Access/Jet does give you the ability to use VBA stored
procedures (like the next version of SQL Server will have),
but the VBA stored procedures aren't available to C++/ASP/VB/.NET
clients, so for all those people, Jet/MDB doesn't support
the kind of stored procedure that they would be interested in.
(david)
"Tim Marshall" <TI****@PurplePandaChasers.Moertherium> wrote in message
news:dg**********@coranto.ucs.mun.ca...
I was following the thread "Re: Access Treeview - Is it Safe Yet?" with
interest and on reading the post describing Lauren Quantrell's SmartTree,
I've run into something I don't understand: Stored Procedures. I thought
stored pricedures were an Oracle/MS SQL Server thing and don't know how
they work with Access Jet. I've looked at some of the help on stored
procedures in A2003, but really don't understand what's going on.
Can someone explain this in a relatively simple way?
Thanks very much in advance for anything on this.
--
Tim http://www.ucs.mun.ca/~tmarshal/
^o<
/#) "Burp-beep, burp-beep, burp-beep?" - Quaker Jake
/^^ "What's UP, Dittoooooo?" - Ditto
