For your first question - if you want them to land on the edit form go ahead and swap out dr with er in your url. So:
URLRoot() & "db/" & Dbid() & "?a=er&dfid=15&rid=" & [Record ID#]
To your second question about opening the parent from the child - it's easy enough with the same format but different field inputs:
URLRoot() & "db/" & dbid of parent & "?a=dr&rid=" & [Related Parent Value Field]
I always recommend using the table alias instead of hard coding the dbid as well
https://helpv2.quickbase.com/hc/en-us/articles/4570272019220-Table-aliases
Thank you! To the first question - how can I have it open in the alternative form in View, but still be able to then Edit from that same alternative form? Both are valuable, and landing in "View" is my preference if I can help it.
The Edit button that QB natively provides will only ever go to the 'Default' form unfortunately - so if you're on form id 15 and hit edit it will always drop you back in the default form. Others probably have their own opinion on ways to do this - to solve it in the short term you can just make your own 'edit' button that you put at the top of the form and try and direct your users there - basically just put the button up top and hope you're users don't click the native edit.
Interesting. I thought it might be something about the way the code was written. Historically, before I learned how to make this button to pop me into the other form, I had a report that was built to access that form - and if you click edit from that, you stay in the form you're in. I just assumed if you got into a form, the edit button would apply to that form, and it must've been something about how I coded the action in the formula URL.
