Posted 21 January 2012 - 10:17 AM
I just entered the following person as a child of my wife and me to illustrate my point:
Name: dr. data Checker esq.
Born: 31 Jan 1867
sant louis' mx
Died: 15 April 2012
St. Louis City, Misouri
The lack of common sense data check routines in RM allow obviously incorrect information, punctuation and spelling errors.
I hope something can be done about this situation soon. What I am pointing out is not a new problem for the information processing industry.
Perhaps pay a Contract Programmer a few bucks????
Posted 21 January 2012 - 11:36 AM
As far as entering data, if it was made "idiot proof", some idiot genius would find a way around it.
Posted 21 January 2012 - 11:58 AM
I'm not at my computer to check, but with CountyCheck turned on you might get an error message.
I did have an error shown when I had a period instead of a comma in the place name.
A visual check of entries before I save the fact saves lots of making corrections later.
Posted 23 January 2012 - 03:57 PM
It was not my wish to start an "oh yeah!" argument here. I mentioned the issue in what I thought was a humorous tone. Thanks for the lesson, now I know.
Alfred, regarding Problem Search reporting function, let me ask you a question. If you can program a data check routine to catch errors after the fact, why not put the code in the data entry function and stop it from coming into the records at all. I suggest you create some of the bad data in one of your records and then see how much of it clears Problem Search. I did and it does not get it all. Bless you Alfred, have a wonderful day...
Posted 25 January 2012 - 07:22 AM
I like the approach of 'flagging' (reporting) errant data, but allowing me to enter what I wish until I can confirm the data is indeed flawed. Its a more flexible approach