General information
Category:
Forms & Form designer
>>>>I created optionGroup class with 3 Options.
>>>>In a table I associated an integer column with that optionGroup.
>>>>When I drop the field on a Form from the table in the dataenvironment I get the warning "member xyz is a member class"
>>>>
>>>>But if I change the Option number in the class from 3 to 2 it works without problem.
>>>>
>>>>What causing that error?
>>>
>>>I don't think it's a good idea to associate a field with some class when you design your table /database. Can you remove the mapping in table designer and see if the error goes away?
>>
>>I don't understand why it is a bad idea. I use it all the time.
>>It works perfect with 2 Options but give me that error with 3 Options.
>
>Ok, just for this one then remove it. I personally don't use the field mappings, but I'm not sure if I can quickly figure out why it is really a bad idea to use them, may be someone else can chime in.
If I remove it I don't have a problem.
When you are working on screen with many fields it is good help to associate a table column with a class.
What puzzling me is why it has problem with 3 Options but not 2??
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only