Re: Duplicate Values Question

My general approach when working with SQL server does NOT include the use of
stored procedures except in rare cases. I use Jet queries with selection
criteria and bind them to forms and reports.

"Jamie Collins" <jamiecollins@xxxxxxxxxx> wrote in message
news:165f846c-21d7-4cf3-9029-b81e0ac2f2c5@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On Jan 18, 9:28 pm, "Pat Hartman" <please no em...@xxxxxxx> wrote:
if the back end were SQL Server, you wouldn't even
consider letting the users at the tables directly.

The general approach in SQL Server land is to create a 'library' of
stored procedures to allow controlled access to the data. And speaking
of SQL Server, the OP could google the term "nullbuster" as a possible
approach to their problem.

Users should NEVER be allowed to work directly with tables or queries.

Drawbridge mentality <g>! If you think that Access 2007 means that Jet
is not dead then it must also mean that user level security in Jet is
dead, which would mean it's even more important than ever for
effective table constraints to be in place to prevent data corruption
via typos by sys admins (i.e. any user) and bugs in front end
applications. Speaking of which:

Create a form in data*** view if that is most comfortable for them.
You
can then put edit code in the various events to validate data.

"The poster was asked about some basic data integrity issue and in the
discussion, he replied that all the validation would be done in the
front end application program, so we did not have to bother with
constraints on the [database] side. Golly gee whiz, do you suppose
that might be a bad idea? Let's just list some of the assumptions and
situations required for this approach to work... This application and
database code will remain the same forever... Nobody else will ever
write new code against this database... If anyone does write new
application code against this database, he or she will always get the
constraints correct and maintain the data integrity... If several
programmers write new application code against this database, they
will always get the constraints correct and identical..."

http://www.dbazine.com/ofinterest/oi-articles/celko25/

Jamie.

--




.