Forum Discussion
JuanSolorio1
5 years agoQrew Cadet
Thanks, Mark!
We had implemented a similar approach with an intermediary table. However, the roadblock we came across was that only one User (or Element) could be viewed at a time. If multiple people were attempting to view these reports simultaneously, they would not be able to because the single record in the intermediary table keeps getting overwritten every time they click the button. Nevertheless, it is the closest we have come to what we are looking for, and it definitely does what we need it to do.
Thanks again!
J
------------------------------
Juan Solorio
------------------------------
We had implemented a similar approach with an intermediary table. However, the roadblock we came across was that only one User (or Element) could be viewed at a time. If multiple people were attempting to view these reports simultaneously, they would not be able to because the single record in the intermediary table keeps getting overwritten every time they click the button. Nevertheless, it is the closest we have come to what we are looking for, and it definitely does what we need it to do.
Thanks again!
J
------------------------------
Juan Solorio
------------------------------
MarkShnier__You
Qrew Legend
5 years agoI do have another approach which I can implement, where the User Focus is stored in a self maintaining table of Users where the Key field is the Userid. But I don't think it's needed, because the click only has to last long enough to refresh the record and see the result.
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------
------------------------------
Mark Shnier (YQC)
[email protected]
------------------------------