Export DB3 Y2K Glitch (AREV Specific)
At 29 FEB 2000 02:50:59PM Warren wrote:
I tested date exports to DB3 files in ARev 3.12 and it is free of the Y2K bug (assumed 19xx dates) that appears in releases 2.12 and earlier . Good work Aaron.
I have not tested v3.0x as the only copy I have is a prerelease beta.
I moved the v3.12 object record $EXPORT.DB3 to v2.12 and it functions normally. I have not yet tried this in v2.03. I'm not certain that 3.12 object code will work with the 2.03 RBasic runtime machine. As I recall there were changes to the compiler/runtime machine at times and recompiling was recommended although the older object code would still run.
So at least for v2.12 using the v3.12 $EXPORT.DB3 is a viable fix for the DB3 export Y2K bug.
At 05 MAR 2000 09:31PM akaplan@sprezzatura.com wrote:
Much as I'd love to take credit for the fix, I didn't touch the code. It was probably Janie. Thanks for the consideration though.
akaplan@sprezzatura.com
[/i]World leaders in all things RevSoft[/i]
At 06 MAR 2000 10:33AM Warren wrote:
The v3.12 EXPORT.DB3 object code works with v2.03, and I see no reason why it shouldn't work with v3.0x.
I have yet to test it with v1.16.
RTI should make the v3.12 $EXPORT.DB3 available for download for users of v2.0x thru v3.0x as a Y2K fix/workaround.
Again, this would solve the problem where all dates that are always assumed to be in the 20th century (e.g. 1900-1999) for export into DBase3 files.
At 07 MAR 2000 09:58PM Chris Leenhouts wrote:
There is a new utility called xPort at http://exorsys.com/revelation.htm which resolves all the technical and conceptual problems asssociated with Revelation database exports.