Hi again,
 
I didn't find a solution to the exact problem, but in case somebody else encounters the same problem I will post what I found out anyway:
 
Astonishingly, the problem does _not_ occur when calling the report from a RunBaseReport class. (Which is okay with me, since I need to do that anyway.)
 
It's a strange world ;-)
 
Bye, Annette
 
-----Urspr�ngliche Nachricht-----
Von: Theissen, Annette
Gesendet: Mittwoch, 24. M�rz 2004 16:58
An: [EMAIL PROTECTED]
Betreff: [development-axapta] __ILLEGAL_VALUE__

Hi everybody,

I am trying to create a report that uses a table with a custom
defined enum. When trying to set a filter to this enum, Axapta
doesn't accept values other than the first and the second enum-entry.
Everything else is replaced by __ILLEGAL_VALUE__.

I do not have this problem when assigning a filter to this table in a
form, but only in a report.

The error occurs if I assign the filter manually, in the report range
or via X++.

BTW: This is Axapta 2.5, no SPs.

I am gratefull for any hints as to how I might solve this problem!

Thanks, Annette



Yahoo! Groups Links

Reply via email to