BTW, do try Doug's suggestion if you haven't already.
Things worth looking at:
a. assuming the value in the query originates from a table, what is the
data type of the column in that table? Although it seems rather unlikely to
me, if it happens to be defined as a "Currency" type column, there are
problems with that type.
b. does the value actually come from a lookup table (this may seem unlikely
given that we're just talking about a number, but in this case I wondered
whether a lookupmight be used, e.g. to limit the possible values to a
particular subset)
c. of maybe the value is calculated in a function?
d. also perhaps worth modifying the query code so that the value is
returned as a specific type, e.g. using the cint() function.
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Lynda" wrote in message
...
kGood Morning:
Yes, I am in a position to look at the definitions in the relevant tables.
However, in this case, the decile generated is calculated in the query so
is not a field in a table. The strange thing is that Word reads the same
calculated field correctly in some cases, but incorrectly in others. It
seems to be random. I have tried everything I can think of, but have not
encountered a solution yet. When I look at the data in Word, the number
has already been changed when Word opens the data source--even though the
number in the query in Access is correct.
"Peter Jamieson" wrote in message
...
Are you in a position to look at the defintions of the relevant tables in
Access?
--
Peter Jamieson
http://tips.pjmsn.me.uk
"Lynda" wrote in message
...
I have an Access database query that computes a student's class rank in
deciles. This works fine in Access, but when I merge it in a Word
Document, Word changes the decile. For example, I have computed a decile
of 4 for a student, but Word displays it as a 10. When I look at the
underlying record source in Word, it shows the 4 as a 10 in the Access
field.
Can anyone tell me what is going on here? Why doesn't Word see the real
number?