[AccessD] Going CRUD way...

Shamil,

I have a stored procedure that I use to generate a
single CRUD that uses "modes" for each table. If you
(or anyone else) would like to get a copy of it,
send me a note off list and I will send a copy of
it to you.

What it does is creates a mode for each of the parts
of the CRUD, Create (I mode), Read(A (All) and S
(single record) modes), Update (U mode), Delete,
(D mode). Plus, I throw in a few other "standard"
ones that we have found useful here. You can also
add in "custom" modes at the bottom that can give you
additional functionality. You can have up to 36 modes
if you use a single character.

Robert

At 10:54 AM 7/30/2007, you wrote:
>Date: Mon, 30 Jul 2007 18:47:16 +0400
>From: "Shamil Salakhetdinov" <shamil at users.mns.ru>
>Subject: Re: [AccessD] Going CRUD way...
>To: "'Access Developers discussion and problem solving'"
>         <accessd at databaseadvisors.com>
>Message-ID: <000701c7d2b8$86cb14e0$6401a8c0 at nant>
>Content-Type: text/plain;       charset="us-ascii"
>
>Hello Arthur,
>
>Thank you for your prompt feedback.
>
>May I say you're a "generated CRUDs fun"? (I'm getting like that here too
>therefore this "generated CRUDs fun" is a respectful nickname here :) ...)
>
>Do you have any samples of small CRUDs, which you use *in production*, which
>therefore proved themselves as stable and which you can publish here? - just
>one for every type of CRUD (Insert, Update, Delete SQL) + Select (by Id)
>SQL...
>
>Thank you.
>
>
>I must say that views used with WinForms (.NET 2.0), even when parameters
>are used but when views are run against large amounts of back-end data -
>such views are (very) slow comparing to parameterized stored procedures.
>
>I do use views but only as a "middle-/abstraction tier" between SPs and base
>tables...
>
>--
>Shamil
>