I performed a test migration to M2M Version 6.0 the other day on a test server. After your test server is set up, one of the first steps is to run DBSCAN on your Util database. My scan found a few records with data corruption. One sample record is below:
11/21/09 03:17:39 PM:dbScan: Data Corruption Detected!
11/21/09 03:17:39 PM:>>Table…..: L:\M2MDATA\\UTIL\utrpsess.dbf
11/21/09 03:17:39 PM:>>Record Number…….: 3995
11/21/09 03:17:39 PM:>>Field Name……: DATE_FROM
11/21/09 03:17:39 PM:>>Error……: Date fields must have values > 01/01/1900
11/21/09 03:17:39 PM:>>——————————————————————————–
To clean this up, I opened VFP and entered the following commands:
set exclusive on open data M:\m2mdata\util\util.dbc use utrpsess goto 3995 brow |
When I hit browse, I didn’t understand the problem. Look for yourself:
Looks like a good date to me.
However, a Consona Support Tech suggested I click inside that field and when I did, I saw the following:
See it?
Score one for support.
David
Wow not quite “Groundhog Day” with Murray but I did have the same experience with (4) four records on my test server.
Thanks
Was that date actually 0006 or did you doctor that for your example? If genuine, why on earth would M2M enter a date of 0006?
The date was actually 0006. To quote those old Tootsie Pop commercials, “The world may never know.”