In your post above you had a URLRoot() in front of the coder that does not belong. That will cause a syntax error.
Will this be used in Mobile mode? The last time I tried to get EOTI working I was unable to get a perfect user experience if I needed the Quick Base Branding and headers all removed and needed a solution which worked well in desktop and mobile mode..
If you set the Advanced properties of the tale to save parent automatically when a child is created, what that actually does is to auto save when you navigate away form the page.
That would allow you to simply have a button to navigate to your dashboard page on the form.
So the button to get to your EOTI form would be
URLRoot() & "/db/bqsxvcdiv?a=nwr&dfid=10&ifv=1"
and then the Submit button would be just be
URLRoot() & "db/" & AppID() & "a=showpage&pageid=5"
But in Mobile mode you will not be able to suppress the native Save button So the best I think that you can do if your users end up in mobile mode is to have a thank you form which is specified as the View form for EOTI Role and to set the form not to show build in fields and to have a Rich text formula field as a thank you message. Maybe a link to get to your Rich text page on the view form.
The issue in mobile seems to be that you cannot suppress the native save button which means that userswill land back viewing that record that they just entered.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.commark.shnier@gmail.com
------------------------------