** In Numeric fields - Clipper

> In checking databases with eroors I find ** in numric fields. Has
> anyone an idea how this can happen ?

check for the lenght of the field and the length of the assigned value
if u have only 2 spaces for numeric u can put number up to 99. If u put 100,
** will be put instead


--
Ciao
Alessandro

On May 21, 7:13 am, "Alessandro Antonangeli"
<alc...@alcati.RemoveThis.com> wrote:
> > In checking databases with eroors I find ** in
> > numric fields. Has anyone an idea how this can
> > happen ?
>
> check for the lenght of the field and the length
> of the assigned value if u have only 2 spaces for
> numeric u can put number up to 99. If u put 100,
> ** will be put instead

Also, -10 will end up the same way (in a length 2 numeric field).

David A. Smith

Lucas

> In checking databases with eroors I find ** in numric fields. Has
> anyone an idea how this can happen ?

The following acan cause that problem
Defined as -
FLD1, N, 2, 0

Try putting a larger number than will fit in the field

FLD1 := 3000

? FLD1 // **

You should also get an error, but your error handler might be suppressing that (if your using one)

--
CYA
Steve

Dear Stephen Quinn:

On May 21, 7:51 am, "Stephen Quinn" <stevej...@SPbigpond.netAM.au>
wrote:
....
> You should also get an error, but your error
> handler might be suppressing that (if your
> using one)

If the table is generated (or just populated) by a third-party
application, there may be no exception raised available to VO.

In other words, he may have inherited this problem. One of the
problems of having a non-proprietary, accessible data platform is that
other applications *can and do* access it.

David A. Smith

On 21 mei, 17:47, dlzc <d...@cox.net> wrote:
> Dear Stephen Quinn:
>
> On May 21, 7:51 am, "Stephen Quinn" <stevej...@SPbigpond.netAM.au>
> wrote:
> ...
>
> > You should also get an error, but your error
> > handler might be suppressing that (if your
> > using one)
>
> If the table is generated (or just populated) by a third-party
> application, there may be no exception raised available to VO.
>
> In other words, he may have inherited this problem. One of the
> problems of having a non-proprietary, accessible data platform is that
> other applications *can and do* access it.
>
> David A. Smith

Thank you all for the responses. I didn't know that putting in a
greater number gave this problem !

Dear Lucas_be:

On May 28, 2:23 am, Lucas_be <lucas...@advalvas.be> wrote:
....
> Thank you all for the responses. I didn't know
> that putting in a greater number gave this
> problem !

It is also possible for an application outside yours to populate a
numeric field with a value larger than what it is formatted for, by
"consuming decimal places". A field formatted ####.### could contain
a value 99999.99, or even 99999999 (???). I have seen Visual Fauxpro
do this, and other code may do this as well.

David A. Smith