Caching Issues on File Links
I typically use this syntax to make a file link field (that i can pass through lookup fields) "<a href='"& URLRoot()&"up/"&Dbid()&"/a/r"&[Record ID#] & "/e6/v0' target='_blank' >" & [Field Name] & ...
Forum Discussion
if V0 is current, does that mean if you had 2 files uploaded, V2 would be the latest version? And if you had 3 files, V3 would be the latest version?
Maybe I can just use V5 and it will default to the latest...?!
------------------------------
Michael Tamoush
------------------------------
Maybe I can just use V5 and it will default to the latest...?!
------------------------------
Michael Tamoush
------------------------------
QuickBaseJunkie
Qrew Legend
Qrew LegendYou would need to know the exact 'latest' version v3, v5, v10... that's what v0 does for you, but as you've called out you then run into the caching issue.
From the QB API Guide "Specifying 0 (zero) for the VID always gets you the most recent version."
------------------------------
Quick Base Junkie
------------------------------
From the QB API Guide "Specifying 0 (zero) for the VID always gets you the most recent version."
------------------------------
Quick Base Junkie
------------------------------
- Is there a way to get the name of each version? Instead of referencing the version as a file link, just reference each version and check it's file name? Then we could use a series of 5 if statements to try to tell it to link a specific version??
------------------------------
Michael Tamoush
------------------------------ - OK. I just tested. If I reference the specific version, it works, so this leads to the question - can we somehow test to see which version we are on? If so, we can defeat the caching issue with a series of if statements.
------------------------------
Michael Tamoush
------------------------------- QuickBaseJunkieThat is the qustion... and one I don't have a direct answer for.
------------------------------
Quick Base Junkie
------------------------------