P
Paolo
Hi,
I think I'm really breaking the rules here. I asked a related question
a couple of weeks ago, and was told that it was ok, but this may tip
things over the edge.
I have a table that is filled with nulls and includes calculation
fields. The reason is the following: Field 1 is a Work Breakdown Code
that can be any length, and feature any number of periods or numbers as
text (xxx.x.xxxx or xx.xxxxx.x.xxxx.xxx, whatever). Field 2 is an
optional field that may or may not be applicable, and field 3 through
12 are the parsed remains of field 1 turned into integers(if field 1 is
13.254.12, then field 3 is 13, field 4 is 254, field 5 is 12 and the
remaining fields are null). I use fields 3 through 12 to sort my codes
as Work Breakdown Codes as text fields do not sort well. So we have:
Field 1 Field 2 Field 3 Field 4 Field 5 Field
6-Field 12
13.254.12 Optional 13 254 12 Null
As you can see Field two and Fields 3-12 are going to be populated with
nulls. I know I can create a one to one relationship with another
table to get rid of Field 2 (there are in reality more than one field
like Field 2), but is it really worth it? I know that I can create a
query that will concatenated Fields 3-12 to create an expression that
looks like Field 1 and thus get rid of the calculation, but then I
would have no primary key and Field 3-12 would still have nulls.
I do hope someone has the patience to wade through this.
Thanks in advance.
Paolo
(e-mail address removed), remove NOSPAM
I think I'm really breaking the rules here. I asked a related question
a couple of weeks ago, and was told that it was ok, but this may tip
things over the edge.
I have a table that is filled with nulls and includes calculation
fields. The reason is the following: Field 1 is a Work Breakdown Code
that can be any length, and feature any number of periods or numbers as
text (xxx.x.xxxx or xx.xxxxx.x.xxxx.xxx, whatever). Field 2 is an
optional field that may or may not be applicable, and field 3 through
12 are the parsed remains of field 1 turned into integers(if field 1 is
13.254.12, then field 3 is 13, field 4 is 254, field 5 is 12 and the
remaining fields are null). I use fields 3 through 12 to sort my codes
as Work Breakdown Codes as text fields do not sort well. So we have:
Field 1 Field 2 Field 3 Field 4 Field 5 Field
6-Field 12
13.254.12 Optional 13 254 12 Null
As you can see Field two and Fields 3-12 are going to be populated with
nulls. I know I can create a one to one relationship with another
table to get rid of Field 2 (there are in reality more than one field
like Field 2), but is it really worth it? I know that I can create a
query that will concatenated Fields 3-12 to create an expression that
looks like Field 1 and thus get rid of the calculation, but then I
would have no primary key and Field 3-12 would still have nulls.
I do hope someone has the patience to wade through this.
Thanks in advance.
Paolo
(e-mail address removed), remove NOSPAM