Are these your relationships? (Though probably with different names)
User::__pkUserID = Reference::_fkUserID
Attributes::__pkAttributeID = Reference::_fkAttributeID
Is "allow creation..." enabled for Reference in the relationship from user to reference? For attributes in the reference to attributes relationship?
How is your layout designed? On what table is it based? Are you using a portal? Leaving ODBC out of the question for a moment, on normally picks a different attribute for user using a portal to reference where you create one new reference record and then link it to an atribute record to show the selected attributte. This method cannot use a single field formatted with multiple check boxes.
And all three tables are from an ODBC source? or just some of them? Is this set up using ESS?
The fact that a user can have many attributes does NOT require the reference table to serve as a Join unless an attribute also must link to many different users. That appears to be the case here, but if I am wrong about that, you can simplify your solution by getting rid of the reference table.
Hi Phil, just got into the office,
those connections look accurate
Yes i turned it on
My layout is basically different info on a specific user, so I am using portals, within one of the portals is the checkbox for attribute reference. The Id in attribute reference should bring up the Attribute Name from the attributes table. I have it setup to show all the attributes now, but it only shows one checked even though the user has multiple attributes, and whenever i try to save another attribute via checkbox it does not save and says
"the field is defined to contain numeric values only. You must enter a numeric value."
all tables are connected to my sql database through odbc
yea attributes link to different users on the same attributes, it is used to group people together in many different groups
I don't quite see how your "check boxes" are set up here as what you describe would only allow for selecting a single attribute for each record in reference--which would normally use a radio button format, not check boxes.
The error you describe suggests that you have a value list of text values but are attempting to modify a field that only permits numeric input.