Hello again Infonaut, welcome or welcome to a new installment of your YouTube channel Infoductiva
this time we will continue with the base of data
and let's see
how to pose the making of a mask entry
for emails
interesting, right?
We start
Well first of all I in the design of the table just created a field called email, text type email ... okay?
with what we've already seen of entrance masks
I ask you to make an effort to reason
what would that entrance mask look like?
if you stop to think about it
you realize that it is not possible to cover introduction of an email to make sure that
comply with the mold of the postal format electronic
through the entrance masks
since there are a great amount of possibilities especially in length of characters and other
let's see ... then!?
if we can not do it with an entrance mask
as we propose to make sure that
do not make mistakes in the introduction of the mold ie
that are valid emails and the database is in charge of controlling this
well, actually, instead of using
an entrance mask we will be forced to use a validation rule
and with it we will have to use a validation text, right?
in principle you have to
assume that there are many types of mail electronic but they all meet
with certain conditions, then
What we intend is that the table ensure that emails
be written
with
at least
the sign of at
agree? a certain number of characters after the sign of @ better said
after there is one or more characters
then a point and finally let's say it would be the domain ... the area excuse me ... well?
that would be a number of characters but we do not know and they are two, one or three, four ... okay?
for example let's see we have to allow that can you write
as a valid email address for example pepito@domain.com this
would be a perfectly valid email address and should be accepted
for our database, according?
but you should not allow for example
Pepito @ domain, com
agree? that is, there are no commas
no semicolon
neither should Pepito @ dominio
all right? you need the scope, you need to add a point whatever
well ... with this premises we will develop as the first validation rule throughout this course
what would be the validation rule that would cover these three needs that I just mentioned
then I select the email field where I want
add this validation rule
and in the properties of the field, here below we are
with validation rule
and then validation text, right?
validation rule is basically an expression that will limit
the introduction of values, according?
It is not the same as the mask but in this case it will do practically the same function since as we have already said
we can not do, it is impossible to generate an authentic entry mask to cover
all email addresses then ... how do we do this? good in principle
this may sound a little weird but basically we would have to say
that we accept that is null ... this supposes like Is Null
respects uppercase and lowercase
that is to say that my validation rule is going to contemplate the possibility
that you leave it blank
okay? because in this case I do not want it to be a mandatory data either
and if it's not null ... it's not null
I have to put Or
that is to say that you have to fulfill what I am going to say next, ok?
in principle this so that you see it with more simplicity
will be included within a quote forgiveness ... inside
of parentheses, right?
and within these parentheses I am going to generate two conditions
okay?
that's why I'm going to open two more parentheses
all right? and here I will say using the command or the Like instruction
that is to say that he likes or that meets this
and in double quotes
I'm going to really put this first validation rule
* it means
I do not know how many characters there are but I accept them
then interrogation that we already saw it
in the previous video when we talk about the input masks, that is, I have to end with a letter
that letter has to be in contact directly with
the @
then
after the @ there can be no other sign than a letter
all right?
I do not know how many letters
that's why I put an asterisk
Point because it will go ... there will be a point after the domain name
and after this will come the field
and the field we put as an interrogation
and as I do not know how many characters ... *
I already know that it sounds a bit like Chinese
but once I finish filling all this
You will see how it is easier for you to understand
well then
after the internal closure I'm going to add a space I'm going to put And that would be equivalent to say Y
and I'm going to open and close other parentheses because here the second part of the condition goes ... I've already said what I want
or how I want it to be but I'm going to point out what I do not want it to be
okay? that is, I am going to limit the condition that I have just defined
or the validation rule that I just defined and in this case I'm going to say Not Like, that is
that I do not like ... that I do not want
all right? and in double quotes
we are going to express that there is what there is to the left
and now I put brackets
all right?
I do not want there to be commas or semicolons ...
agree?
with this ...
well I'm going to finish it, after the bracket we would not know how many characters there are to the right
agree?
and that's it ... Is Null Or ((Like "*?@?*.?*") And (Not Like "* [,;] *"))
we would have our first
validation rule
finished ... by giving Enter as you see, the Is Null has changed
by the nomenclature in Spanish because I have my operating system in this language
but hey ... it does not matter remember this
let's say it's a language like it happens in some questions
in Excel that changes depending on the language you're using ... although I've started with Is Null and I've put here Like and here Not Like
basically he translated it into Spanish
It is null
or
I open two parentheses
first condition would be the second parenthesis up here
and here what I am basically saying is that
I want and I put in double quotes everything that I want
and there I define let's say that the mold
I'm saying that I want the characters that there is just to the left of the arroba has to be letter
on the right it also has to be letter then there may be the amount of characters that there is that is *
there has to be a point below then in contact with that point it also has to be a letter
and with the last * I'm saying that the number of characters that are ... right?
we close
the quotes and parentheses so here how do you see is the first part
next we use the conjunction Y
and again inside the parentheses we are saying that we do not want
That Not Like or No Like what the translation would be but Not Like is better understood
and in double quotes I'm saying what I do not want, where I'm saying it does not matter
the number of characters on the left or on the right, which is symbolized by the asterisks
I do not want any of those characters inside of me
email address ... okay?
I press enter again ... if it was not correct or I would have been confused
in the form of expressing it
I would give an error, I urge you to analyze part of these blocks that I just defined
and then we would need to put
a validation text, a text that will serve to notify the user
agree? then for example
let's put as validation text
You must write
remember that this is let's say a legend for the user who uses the database
you must write
one direction
of email
correct
and valid
with
@
and the domain name
and its scope
and here what we are going to put, in parentheses for example is ... for example ... worth the redundancy
in quotes I will put
pepito@servidor.es
pepito@servidor.es
I close the quotes and close the parenthesis ... okay?
in such a way that we are warning
to the user of the database that he must write
a valid and valid email address with the @ and the domain name and its scope
for example pepito ...
sorry I have confused I put pad ... we correct it
pepito@servidor.es
pepito@servidor.es
pepito@servidor.es ... press Enter ... that's it ... we already have it
next we are going to close the design of the table ... let's say that if
the integrity rules have been changed so that not all the data
are saved, this means or you are telling me that you should enter the email address of the other users
we say yes and then double click on the table ...
we are going to move
to see here on the right the email ... I'm going to enlarge it a bit
and then I'm going to put a fake email ... for example
mamapepito
mamapepito
mamapepito @
mamapepito @ gmail
and I leave it like that ... I give Enter and he tells me not to
What should it be ... see? here would be the validation text
here we would be reading what we have written as validation text ... we will accept then I will finish with
mamapepito@gmail.com ... as you see I give to enter and if you accept it
all right? so that's how I just made sure
that is not possible
enter an invalid email address ... I will put here
mom
mamafulanito
mamafulanito @
mamafulanito @ hotmail
mamafulanito @ hotmail, is ... I'm going to put a comma to make a mistake and the same
Hey, it can not be, you have to write it correctly
and it's because of the comma that I just added, remember the not like that we just introduced so I'm going to put a point
all right? so I make sure that a lot of the review work
it is done by my validation rule for introduction of the input data
here I will put papaandrea
papaandrea @ gmail
papaandrea@gmail.com
and in this I'm going to put
papajulia
papajulia @
papajulia @ hotmail
papajulia@hotmail.es
agree?
how do you see now we have a much greater control
of data entry
thanks to the input masks we gave in the previous video for dates of birth
and phone numbers
and now with the validation rule that we just play in this video and having understood
why can not we use an input mask to cover all this data
and yes a validation rule
we have a lot of the mistakes that would happen overlooked and then they would give us problems
in the long run ... As you can see, it is very useful, we could say that it is practically essential ...
Well that's it
thank you very much for sharing my videos on your social networks ...
thanks for subscribing and for activating the notification bell ... thank you very much for your comments and for your Likes ... see you
in a new installment of your YouTube channel Infoductiva ... See you soon Infonaut ...
No comments:
Post a Comment