Data expression error and data conversion error

[Bob Comeau]

We got a "data expression error" on a quick screen that updated a sequential
counter and that counter had reached it's maximum value.   I believe it was
zoned decimal with 5 positions and had a value of 99999. Adding one to it
caused the data expression error and the value that got used as a result
was difficult to decipher but it came coming up with the same value.
This value became part of a key used in another file.  So the problem
only became apparent when the rest of the key was the same also.  That
cause a "data access error" when they tried to update the screen.

Don't know if this applies at all to your situation at all, just thought I'd
pass
it on.

(We got passed the problem by resetting the counter to 00001, the oldest
record still in the file had a counter in the 40000 range, we have about two
years before it's a problem again.)

Bob Comeau

-----Original Message-----
From: powerh-l-admin@cube.swau.edu
[mailto:powerh-l-admin@cube.swau.edu]On Behalf Of Michael Lee
Sent: Friday, August 10, 2001 12:35 PM
To: Pickering, John (NORBORD)
Cc: 'MacDermott, Paul'; 'powerh-l@list.swau.edu'
Subject: Re: Data expression error and data conversion error


Paul,

I agree with John. I would first focus on any DEFINEs that you use the
NCONVERT
function first. If you try to do an NCONVERT on an item which contains
something
other than numbers 0 through 9-you will get a data conversion error. If it's
not
those specific items-find out what you then do with those DEFINEs after you
do
the conversion.


Michael Lee
MCL Systems Inc.

"Pickering, John (NORBORD)" wrote:

> 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
> >
>
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l@lists.swau.edu
> Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
> Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
> http://lists.swau.edu/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.