Roman Numeral

[T5925MS via AccessMonster.com]

I have a text field that contains roman numerals. Why does my report convert
that roman numeral to a number when I concatenate it with other fields?

 

[Marshall Barton]

I have a text field that contains roman numerals. Why does my report convert
that roman numeral to a number when I concatenate it with other fields?

Because the field's value really is a number? This could
happen if the field is a lookup field.

It would help if you could figure out how you are getting a
roman numeral when you do not concatenate it. Maybe it
would also be useful to know where/how the roman numeral is
entered into the field.

 

[T5925MS via AccessMonster.com]

When I put the field in by itself, RomanNumeral vs =[RomanNumeral], it does
not convert it to a number. Also, I enter roman numerals into each field
manually, i.e. IX or XIII etc. Thanks for your response.

 

[Marshall Barton]

That's a real head scratcher. I Never heard of such a thing
without using some code (in the section's Format or Print
event) to explicitly convert it. Maybe that's some kind of
new feature in A2007, if that's what you are using?? What
does the text box have in its Format property?

Have you tried to put a break point in the Format/Print
event to see what Access thinks the value of the field and
control is?
--
Marsh
MVP [MS Access]

When I put the field in by itself, RomanNumeral vs =[RomanNumeral], it does
not convert it to a number. Also, I enter roman numerals into each field
manually, i.e. IX or XIII etc.

Because the field's value really is a number? This could
happen if the field is a lookup field.

It would help if you could figure out how you are getting a
roman numeral when you do not concatenate it. Maybe it
would also be useful to know where/how the roman numeral is
entered into the field.

 

[T5925MS via AccessMonster.com]

I'm using A2007. I just realized that it's not converting the roman numeral
to a number. When I put the field in as =[AdminProgCriteriaRomanNumber]
rather than AdminProgCriteriaRomanNumber, the result is the value of another
field called AdminProgNumber. And, it doesn't do this on any other report in
my database, only this report! I value any suggestions.

That's a real head scratcher. I Never heard of such a thing
without using some code (in the section's Format or Print
event) to explicitly convert it. Maybe that's some kind of
new feature in A2007, if that's what you are using?? What
does the text box have in its Format property?

Have you tried to put a break point in the Format/Print
event to see what Access thinks the value of the field and
control is?

When I put the field in by itself, RomanNumeral vs =[RomanNumeral], it does
not convert it to a number. Also, I enter roman numerals into each field

[quoted text clipped - 10 lines]

 

[Marshall Barton]

I'm using A2007. I just realized that it's not converting the roman numeral
to a number. When I put the field in as =[AdminProgCriteriaRomanNumber]
rather than AdminProgCriteriaRomanNumber, the result is the value of another
field called AdminProgNumber. And, it doesn't do this on any other report in
my database, only this report!

Check the control names for both fields, maybe you got those
mixed up too.

IF that has something to do with it, then its an argument in
favor of renaming controls so they are not the same as a
field name.

 

[T5925MS via AccessMonster.com]

Problem solved! You were right. The control names were the same. Once I
ensure they were different, it displayed the correct values. Great suggestion
about making control names different than field names.Thanks for your help!

I'm using A2007. I just realized that it's not converting the roman numeral
to a number. When I put the field in as =[AdminProgCriteriaRomanNumber]
rather than AdminProgCriteriaRomanNumber, the result is the value of another
field called AdminProgNumber. And, it doesn't do this on any other report in
my database, only this report!

Check the control names for both fields, maybe you got those
mixed up too.

IF that has something to do with it, then its an argument in
favor of renaming controls so they are not the same as a
field name.