Re: Validation Rule for field

Where did I say Access for 30 years? I said application and database design.
Only 6 years in Access. Languages and Databases are all pretty much the same
conceptually.

Access, as well as other products, put features and functions into products
that may or may not be good ideas, but the help sell product.

Putting validation in tables and fields is one of the ways Access caters to
the non professional or less experienced designer. As long as you know you
will never upsize to SQL Server, Oracle, DB2, or another engine, then it is
okay.

In my world, I have to always consider that possibility. I try to design
and code my applications so they can be ported to other database engines and
VB with minimul modifications.

I wouldn't know about versions any earlier thn 97. That was the current
version when I started with Access. I moved from 10 years with Foxbase and
Foxpro to Access.

I apologize for the original statement that upset you. I do not mean that
you are not competent or knowledgeable. In my opinion field level validation
has some restrictions that I don't want to deal with. For example, in the
current application I am working with, there are some business rules that
change validation rules for a field based on values in other fields. Can you
do that with field level validation?

"Steve Schapel" wrote:

> Klatuu,
>
> Access has only been in existence for 12 years. And even then, I don't
> remember whether version 1 and 1.1 had table-level Validation Rules. So
> your reference to 30 years is way off, with regard to the topic we have
> been discussing.
>
> I hope you haven't been under the impression I have ben trying to
> convince you of anything. This is not my intention at all. When you
> stated "Absolutely wrong. Never put validation rules in tables", you
> made it sound like you know what you're talking about, and I just wanted
> to point out to other readers that this is not so.
>
> --
> Steve Schapel, Microsoft Access MVP
>
>
> Klatuu wrote:
> > Steve,
> > We obviously have different opinions on this. You will not convince me nor
> > I you. After 30 years of database and application design, I have developed
> > approaches that work for me. I am sure your's work for you.
> >
>
.

Relevant Pages

  • C# programmer looking for a job
    ... Software Development including Desktop, Client/Server and Database ... Practical skills in object oriented design and design patterns ... XML, Oracle, CVS, VSS, Delphi, bug tracking. ... Developed in Delphi5; ...
    (misc.immigration.usa)
  • Re: O/R Mapper
    ... | - create E/R model from niam model ... classes that contain, not only data, but also functionality as OO design is ... a database where they do not exist in the object model is corrupting the ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Date range on reports
    ... > box to your report with a control source like: ... >> In the Database window (Database window: The window that appears when you ... >> In the New Form dialog box, click Design View, and click OK. ... >> Begin by clicking Macro Names to display the Macro Name column. ...
    (microsoft.public.access.reports)
  • Re: limit of lines?
    ... And this is the fundamental mistake in your design. ... a objects from a database, this usually leads to very poor design. ... Framework in which all properties are backed, not by a simple field, but by ... we have major size projects that use the Delphi template ...
    (borland.public.delphi.non-technical)
  • Re: O/R Mapper
    ... > as OO design is not just about data in isolation. ... the proper tooling/methods are used which fit with the approach chosen. ... >> of the reality to come to the proper result. ... > constraints into a database where they do not exist in the object ...
    (microsoft.public.dotnet.languages.csharp)