Data expression error and data conversion error

[Pickering, John (NORBORD)]

Paul

I've never seen this message when it wasn't related to non-numeric data
where Quick was expecting numeric. 

Check all of the define and item statements -- is every one of them strictly
alphanumeric?, could anything in the definitions be junk? 

Check every place you do any mucking about with dates -- Quick expects valid
dates.

Check the linkage specifications to reference files -- since they're usually
optional lookups the screen will appear to work but the data conversion in
the access statement will result in either no record or the incorrect
record.

Let us know what you find.

Regards,
JWP

> -----Original Message-----
> From:	MacDermott, Paul [SMTP:paul.macdermott@eds.com]
> Sent:	Friday, August 10, 2001 5:11 AM
> To:	'powerh-l@list.swau.edu'
> Subject:	Data expression error and data conversion error
> 
> Good mornings folks,
> 
> The latest problem I am encountering is where the error message Data
> expression error or Data conversion error appears at the bottom of the
> screen. All the data on the screen is alphanumeric so I do not think it is
> an alpha in a numeric field and all the data displayed is correct. However
> the appearance of the message is very disconcerting. Has anybody seen this
> type of error message? Do you know what I need to do to prevent it?
> 
> our development environment is Axiant 4Gl version 2.03 for a VMS.
> 
> 
> Paul Mac Dermott
> 
> EDS Ireland
> Treasury Building
> Lower Grand Canal Street
> Dublin 2, Ireland
> 
> *	paul.macdermott@eds.com
>