How do I add decimals to crosstabs in Access?

[Ted Sylvio]

The decimal places are dropped off of the query when I run a crosstab query
in Access 2007. I tried editing the properties in design view and it's not
working.

 

[Dale Fye]

Ted,

If you are talking about decimal places being replaced in column headers
with an underscore, I think you are out of luck. I have never found a way to
do this, and have tried replacing the numeric values with strings.

Access Help (search on "field name constraints") says:

Names of fields, controls, and objects in Microsoft Access:

- Can be up to 64 characters long.
- Can include any combination of letters, numbers, spaces, and special
characters except a period (.), an exclamation point (!), an accent grave
(`), and brackets ([ ]).
- Can't begin with leading spaces.
- Can't include control characters (ASCII values 0 through 31).
- Can't include a double quotation mark (") in table, view, or stored
procedure names in a Microsoft Access project
..
Although you can include spaces in field, control, and object names, most
examples in the Microsoft Access documentation show field and control names
without spaces because spaces in names can produce naming conflicts in
Microsoft Visual Basic for Applications in some circumstances.

When you name a field, control, or object, it's a good idea to make sure the
name doesn't duplicate the name of a property or other element used by
Microsoft Access; otherwise, your database can produce unexpected behavior in
some circumstances. For example, if you refer to the value of a field called
Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
displays the value of the table's Name property rather than the value of the
Name field.

Another way to avoid unexpected results is to always use the ! operator
instead of the . (dot) operator to refer to the value of a field, control, or
object. For example, the following identifier explicitly refers to the value
of the Name field rather than the Name property:

HTH
Dale

 

[Ted Sylvio]

Hi Dale,

Thanks for your post it was informative, but that is not the problem I'm
running in to. The problem I'm having is the actual values that are pulled
when the query runs are lacking any decimal places.

Ted,

If you are talking about decimal places being replaced in column headers
with an underscore, I think you are out of luck. I have never found a way to
do this, and have tried replacing the numeric values with strings.

Access Help (search on "field name constraints") says:

Names of fields, controls, and objects in Microsoft Access:

- Can be up to 64 characters long.
- Can include any combination of letters, numbers, spaces, and special
characters except a period (.), an exclamation point (!), an accent grave
(`), and brackets ([ ]).
- Can't begin with leading spaces.
- Can't include control characters (ASCII values 0 through 31).
- Can't include a double quotation mark (") in table, view, or stored
procedure names in a Microsoft Access project
.
Although you can include spaces in field, control, and object names, most
examples in the Microsoft Access documentation show field and control names
without spaces because spaces in names can produce naming conflicts in
Microsoft Visual Basic for Applications in some circumstances.

When you name a field, control, or object, it's a good idea to make sure the
name doesn't duplicate the name of a property or other element used by
Microsoft Access; otherwise, your database can produce unexpected behavior in
some circumstances. For example, if you refer to the value of a field called
Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
displays the value of the table's Name property rather than the value of the
Name field.

Another way to avoid unexpected results is to always use the ! operator
instead of the . (dot) operator to refer to the value of a field, control, or
object. For example, the following identifier explicitly refers to the value
of the Name field rather than the Name property:

HTH
Dale
--
Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

The decimal places are dropped off of the query when I run a crosstab query
in Access 2007. I tried editing the properties in design view and it's not
working.

 

[Dale Fye]

Post your SQL.

Hi Dale,

Thanks for your post it was informative, but that is not the problem I'm
running in to. The problem I'm having is the actual values that are
pulled
when the query runs are lacking any decimal places.

Ted,

If you are talking about decimal places being replaced in column headers
with an underscore, I think you are out of luck. I have never found a
way to
do this, and have tried replacing the numeric values with strings.

Access Help (search on "field name constraints") says:

Names of fields, controls, and objects in Microsoft Access:

- Can be up to 64 characters long.
- Can include any combination of letters, numbers, spaces, and special
characters except a period (.), an exclamation point (!), an accent grave
(`), and brackets ([ ]).
- Can't begin with leading spaces.
- Can't include control characters (ASCII values 0 through 31).
- Can't include a double quotation mark (") in table, view, or stored
procedure names in a Microsoft Access project
.
Although you can include spaces in field, control, and object names, most
examples in the Microsoft Access documentation show field and control
names
without spaces because spaces in names can produce naming conflicts in
Microsoft Visual Basic for Applications in some circumstances.

When you name a field, control, or object, it's a good idea to make sure
the
name doesn't duplicate the name of a property or other element used by
Microsoft Access; otherwise, your database can produce unexpected
behavior in
some circumstances. For example, if you refer to the value of a field
called
Name in a table NameInfo using the syntax NameInfo.Name, Microsoft Access
displays the value of the table's Name property rather than the value of
the
Name field.

Another way to avoid unexpected results is to always use the ! operator
instead of the . (dot) operator to refer to the value of a field,
control, or
object. For example, the following identifier explicitly refers to the
value
of the Name field rather than the Name property:

HTH
Dale
--
Don''t forget to rate the post if it was helpful!

email address is invalid
Please reply to newsgroup only.

The decimal places are dropped off of the query when I run a crosstab
query
in Access 2007. I tried editing the properties in design view and it's
not
working.