decimal places for .1, .10, .100

[Mrs.Meeker]

I've been doing some reading in the archives and can't find a solution to my problem.

I have a table (tbl_QualityControl)with several hundred questions. These questions are coded to relate to different work types. Some questions may relate to 1, 2 or all of the codes. In trying to normalize my data, I duplicated the questions that relate to multiple work types. I then created a numbering system to follow these codes...obviously a poor choice! I have numbers such as 4.10, 1.100, etc. Access is dropping off the zero's. I moved the table to exel to add these codes (faster) and then imported it back into access.

My question is, first, can I fix this? Second, should I change the code to something else before I get in much deeper? Any suggestions? There are 14 codes. (I used 2 to 15...don't ask!)

It's attached if you want to see it.
thanks! Rhonda

 

[WayneRyan]

Rhonda,

In the table's Design View set the format to #.000

It might have better to split the Code into two fields ...

Wayne

 

[Mrs.Meeker]

Hi Wayne,

I'd be glad to split this into 2 fields. I'll work on that tomorrow. I'm assuming 1st cell is the whole number, and the other cell is the decimal, but without the decimal??

I might need some help putting that together

I sometimes feel like I'll always be a "beginner"!!

I have a column containing "the whole number" (before the decimal point) I'm thinking I can remove the first half of the number from the other column.

I have this in Excel again (just to do this part) I seem to be able to fly through that faster. I was told to format it as text, but if I have it split into 2 columns then I should keep it at number; right?

Thanks!
Rhonda

PS I tried the #.000 and ended up with everything with 3 digits after the decimal. That was not acceptable. (Of course I may have done it wrong!)

 

[WayneRyan]

Rhonda,

Oops, I thought that was what you wanted.

Wayne

 

[raskew]

Rhonda-

Gee, wish folks would convert their later Access downloads to Acc 97 so us dinosaurs could follow along.

Having said that, your scenario sounds like it might benefit from the Students and Classes template approach.

A junction table between tblWorkType and tblQuestions would allow you to tailor your questions to specific worktypes.

Take a look at the template and, if my response still isn't clear, please post back and I'll conjur up an example.

Best Wishes - Bob

 

[Mrs.Meeker]

Wayne, if I have 3 digits after each decimal it reads; 4.1 = 4.100, 4.10 = 4.100, 4.100 = 4.100. That doesn't do me a lot of good. But what would I do if I had this broken down into two columns?

Bob, I'm sorry I can't convert to 97, they took it away from us.

I hate to sound like an idiot (so often) but where is the template?

Thanks all!
Rhonda

 

[Mile-O]

I can't convert to 97, they took it away from us.

I hate to sound like an idiot (so often)

Selective quoting...

It's in the Access menu. Convert to Access 97 format or Convert to previous version

 

[Mrs.Meeker]

Oh GAWD I think my brain has fallen out!!! Since they took the 97 version off my machine I thought....well I just won't go there!

Thank you Miles for steering me in the right direction!!! I'm glad that at least I can amuse you!!

Here's the older copy. At least I learned (or relearned?) something today.

With great thanks from a befuddled old lady!
Rhonda

 

[WayneRyan]

Rhonda,

Right now, you are storing this as a number. I see what you
say about the 4.1, 4.10, and 4.100. You are trying to make
Access think that they are not equal. That's not a nice thing
to try to make it do.

There are two solutions: change it to a text field or change
it to two numeric fields.

If you change it to a text field, then initially may seem seem to
be fairly easy. But you will soon see that in string format
that 4.11 comes before 4.2. Like in paragraph #s. This
is the other side of the numeric approach. Each has its own
pitfalls.

You have to bite the bullet and create two new numeric fields.
Then they'll appear in the right order on reports, etc. and there
won't be any ambiguity when called upon.

See ya,
Wayne

 

[Mrs.Meeker]

Thanks Wayne. I've put it in two number fields.
Rhonda

 

[jeremie_ingram]

WayneRyan has the answer, and something that is good to keep in mind. Anytime you have a field that contains a number that WILL NOT BE USED IN CALCULATIONS (phone #, SS #, your number) you should format that field as text. This will not only allow for the type of formatting you want, but allows you to set the field formatting as well.

 

[Mrs.Meeker]

thanks for the tip. These numbers will not be used in calculations so they should be text. They are heading numbers.