ContributionsMost RecentMost LikesSolutionsSecondary KeysI'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.Re: Record Creation DelayedThanks for the response. I guess the problem is that in either case I need to make the user take action -- either scroll down or click a tab -- in order to see the new record. I don't think it's the best solution but I guess it's an easy one. If I'm feeling motivated I may still try to do something with AJAX.Re: Record Creation DelayedGood to know. A solution might be to code some custom ajax to check for the record and not forward the user until it exists. If I end up doing that I will post some example code here. Record Creation DelayedI have a URL which creates two related records, via an automation, and returns the user to a page. It definitely seems as if there is a small delay between clicking this button and when one of the records shows up in a report. For instance, if I click the button and land on the page, and then immediately click a link to go to a report the new record does not appear. But if I wait a moment it does appear. This is problematic. Any suggestions?Re: HTML Code Page is displaying the actual codethat helped me. thanks.