Anyone know a way to overcome the global date option
(6 char) on census DERs because Qtech forces either a century 19 or century 20 option for all dates in the routine. Excel defaults to 20 if year is less than 30.
But this doesn't solve the 5.0 DCM imports where we have encountered plan entry dates or term dates that are last year and current year being returned by clients using 4.1 DCM systems. This means we will need to supply all clients with new DCM systems and use 8 character dates from now on or interrogate closely each client DAT file. I have talked with one of the Qtech programmers who says no mods are planned for 5.1 or 6.0 to change this.
Also... 5.0 documentation states the need to convert our DERs for 5.0, but customer support says "no need" until we go to 5.1. What's with this? I assume conversion does not
do anything to overcome the date problem.

one 'workaround' if you have downloaded 'bad' dates (I have done it, it is easy enough to do), is to export your date fields and subtract 36525 from nay date field you want to read 19xx rather than 20xx. at least on large plans, this is by far the easiest way to go.