date conversion giving "default language set" (AREV Specific)
At 17 MAR 1999 07:20:17PM Peter Fisera (Synergy Computer Consulting) wrote:
Something very strange: it only happened once, but a piece of code that should have created a PERFORM statement like:
SELECT CLAIMS WITH LATEST.TRN.DATE ]= "01 Jan 1999"
instead, according to the TCL command stack, was executed as:
SELECT CLAIMS WITH LATEST.TRN.DATE ]= "01 Default language set 1999"
Needless to say, the conversion failed and this was equivalent to LATEST.TRN.DATE ]= null.
Any idea why this could happen? AREV 2.11 is the version, if that makes a difference.
At 18 MAR 1999 10:13AM [email protected] - [url=http://www.sprezzatura.com]Sprezzatura Group[/url] wrote:
I've seen it happen once and it never happened again. We finally decided it had something to do with low memory and stopped searching.
At 20 JAN 2000 03:48PM Jill wrote:
I have seen reports of this from users all over the country (more reports on our support lines each day)and know for a fact it is not memory related. It is somehow related to the date pass between certain versions of dos and the application running arev. It would be nice if arev would look into this and find out what the problem is. Accessing the app from different shortcuts on the same machine can make a difference as well as calling different bat files. It is happening on Win95/Win98/and NT work stations. Novelle or NT platforms do not make a difference. However if Arev responds in their usual manner we will figure out the answer to the problem with their product long before they admit it exists.