Roman Numeral
in [Reports]
|
From: T5925MS via AccessMonster.com on 22 Feb 2010 11:13 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? -- Message posted via http://www.accessmonster.com
From: Marshall Barton on 22 Feb 2010 13:00 T5925MS via AccessMonster.com wrote: >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. -- Marsh MVP [MS Access]
From: T5925MS via AccessMonster.com on 22 Feb 2010 17:49 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 wrote: >>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. > -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-reports/201002/1
From: Marshall Barton on 23 Feb 2010 12:57 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] T5925MS via AccessMonster.com wrote: >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. > >Marshall Barton wrote: >>>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. >>
From: T5925MS via AccessMonster.com on 23 Feb 2010 13:25
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. Marshall Barton wrote: >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] >>>would also be useful to know where/how the roman numeral is >>>entered into the field. -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-reports/201002/1 |