leading zero's were lost
From: hwylie (anonymous_at_discussions.microsoft.com)
Date: 02/28/04
- Next message: hwylie: "leading zero's were lost"
- Previous message: Mudassir Iqbal: "Parameter Query"
- In reply to: anonymous_at_discussions.microsoft.com: "leading zero's were lost"
- Next in thread: hwylie: "leading zero's were lost"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 28 Feb 2004 03:00:27 -0800
Define the field that receive the "0000123" data as Text.
Currently it is being seen as and stored as a number -
i.e. you don't need leading zeros on real numbers so it
chucks them. Remember what you want the computer to see
and it will interpret the data accordingling. See the
data properties in the table and queries. you can get
some very interesting and completely unexpected results it
you don't manage the movement of data between different
types of data, i.e. character, logical, integer short,
integer long, decimal, real short, real double, etc...
your problem occured becase the computer converted text to
integer long when in fact you wanted text to text.
Hunter
>-----Original Message-----
>I have a problem where I cannot control the format of the
>data I recieve. Some of the data comes to me with the
>leading zero's dropped. i.e. intead of 000352 I get 352
>or 007892 comes as 7892. The # of characters varies, 7 is
>the max it should have to as few as 1 may be reported .
>they all should be 9 characters to work correctly for
>what I am doing. How can I restore the leading zeros when
>the # of charcters varies from recored to record?
>
>123 should be 0000123
>3521 should be 0003521
>69871 should be 0069871
>.
>
- Next message: hwylie: "leading zero's were lost"
- Previous message: Mudassir Iqbal: "Parameter Query"
- In reply to: anonymous_at_discussions.microsoft.com: "leading zero's were lost"
- Next in thread: hwylie: "leading zero's were lost"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
