One of the simplest validations is checking if a date is probably or not. If you do not validate dates you could end up with just about any year. Say a user flubs the appointment date as 9/30/221. Whoever had the appointment on 9/30/2012 is going to be mighty upset when he goes in and the scheduler says he has no appointment.
In this case, assuming no appointment would ever be made more than a year out, a simple check would be to see if the date is greater than Now() and less than DateAdd("y", 1, Now())
As to what major errors could occur, it really depends on the data stored and how it is used.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
https://mvp.support.microsoft.com/profile=C4D9F5E7-BB03-4291-B816-64270730881E
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com, MEL <girl_moon_godess@...> wrote:
>
> What are major programming errors that have occurred because data validation techniques were not used.
>
>
> Thanks
>
>
> [Non-text portions of this message have been removed]
>
Senin, 17 September 2012
[MS_AccessPros] Re: Data validation techniques
__._,_.___
.
__,_._,___
Langganan:
Posting Komentar (Atom)
Tidak ada komentar:
Posting Komentar