Forum Discussion
QuickBaseCoachD
7 years agoQrew Captain
The other syntax is this to execute sequential URL calls
$URLONE
& "&rdr=" & URLEncode($URLTWO)
& URLEncode("&rdr=" & URLEncode($URLTHREE))
& URLEncode(URLEncode("&rdr=" & URLEncode($URLFOUR)))
& URLEncode(URLEncode(URLEncode("&rdr=" & URLEncode($URLFIVE))))
& URLEncode(URLEncode(URLEncode(URLEncode("&rdr=" & URLEncode($URLSIX)))))
You define the formula variables and need to end with one that displays a record or a report.
But Chayce, yours could probably be made more generic for the situation where you want to refresh whatever page you are on. That way it would be more flexible to be used on a record or a report or an embedded child table on a form and be superior to mine for that situation. Is there a change to yours possible which would do that?
$URLONE
& "&rdr=" & URLEncode($URLTWO)
& URLEncode("&rdr=" & URLEncode($URLTHREE))
& URLEncode(URLEncode("&rdr=" & URLEncode($URLFOUR)))
& URLEncode(URLEncode(URLEncode("&rdr=" & URLEncode($URLFIVE))))
& URLEncode(URLEncode(URLEncode(URLEncode("&rdr=" & URLEncode($URLSIX)))))
You define the formula variables and need to end with one that displays a record or a report.
But Chayce, yours could probably be made more generic for the situation where you want to refresh whatever page you are on. That way it would be more flexible to be used on a record or a report or an embedded child table on a form and be superior to mine for that situation. Is there a change to yours possible which would do that?
QuickBaseCoachD
7 years agoQrew Captain
Thx for posting that. The other advantage of the javascript method is that if you get really deep with nesting the URL gets exponentially longer due to the nested URLEncodes and eventually it gets over 2,000 characters and some Browsers like IE have limits on URL length.