MosesBlumenstie
7 years agoQrew Trainee
Secondary Keys
I'm used to other types of database systems (Filemaker, MySQL, etc) which allow secondary non-unique keys and I'm wondering why this isn't possible in Quick Base. Is it simply a limitation or am I missing something?
Here's an example of where I ran into trouble. I have a 'teams' table as parent which relates to a 'team members' table. 'Team member' has a user field. I would like that user field to be a key field for other tables further down the tree but I also want users to belong to more than one team. Normally this would be easy with secondary keys but in Quick Base it gets very cumbersome.
Here's an example of where I ran into trouble. I have a 'teams' table as parent which relates to a 'team members' table. 'Team member' has a user field. I would like that user field to be a key field for other tables further down the tree but I also want users to belong to more than one team. Normally this would be easy with secondary keys but in Quick Base it gets very cumbersome.