validation rule in a form

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
this may sound silly question, but I am preplaxed
Is validation rule created in table is valid in an autofrom created for the
same table? or Do I have to do some modifications in properties of form or
autfrom? If so how?
Right now validation rule giving me desired result for table but not for the
same autoform.

I will be thankful if you can tell me what wrong I am doing? Or what should
I check?

Thanking in advance
Rathi
 
And Also, I don't know VB language as I am not software engineer, as I am
Chemical engineer? So how important is for me to know VB to make database
(personal) very robust and highly reliable?

Thanks once again

Rathi
 
Hi Rathi,

A control on a form that is bound to a field with a validation rule defined
at the table level should cause the validation rule to be observed on the
form, whether you created the form from scratch or used the Autoform wizard.
Right now validation rule giving me desired result for table but not for the
same autoform.

This does not sound possible. Are you sure that the form's recordsource is
the same table?


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 
Hi Hi Rathi,

I am a chemist, and I think it is pretty important to learn VBA (Visual
Basic for Applications) if you want to go beyond just trivial applications
possible without code. Here is a quote regarding macros that I like to share:

From: "Inside Relational Databases, 2nd Edition, by Mark Whitehorn and Bill
Marklyn, published by Springer, p 151

<Begin Quote>

"Macros offer the next level down, extending the functionality of the GUI.
Macros are still limited, however, and do not provide anything like the
enormous flexibility of a programming language. Both the macro and the
programming languages take some effort to learn and, surprisingly, often
require relatively different skills; in other words, a good working knowledge
of macros may not make it much easier to convert to using the programming
language. Perhaps even more surprisingly, I do not believe that programming
is fundamentally more difficult to learn. Macros are easier to use but not by
orders of magnitude."

"If you are new to RDBMSs, I suggest (with as much deference as possible)
that you may well not be in a position to judge whether you need macros or
programming. In that case, my advice is clear. Unless you are sure that your
needs really are simple, don't bother learning to use macros. Once you find
that you need more than the GUI offers, go straight to the programming
language. In this way you avoid the pain of climbing one learning curve only
to discover that the view from the top is unsatisfactory and another climb
awaits you."

<End Quote>

Although macros have been significantly enhanced in Access 2007, I believe
that this just raises the height of the mountain somewhat; I believe one will
still find the view unacceptable in the long run.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Access Validation rule of 1 field based on a field of another table 1
Validate a Date 1
multiple validation rules 3
Validation Rule in Access 2007 3
Validation Rule 1
Validation Rule 2
Validation Rule assistance 0
validation rule 1

Back
Top