Let’s suppose a user works with a large dataset - too large to fit on one screen. In fact, it fills many screens. To get to the outer areas of the data range, this user scrolls or uses [Ctrl]+[RightArrow] and [Ctrl]+[DownArrow]. When you show her a quick trick for moving to the last cell to the right or to the bottom of the data range, she’s thrilled! What did you show her?
Last week we asked…
Hiding a fixed query is easy enough; hiding a query generated by code is another matter. First, I’d want to know why - is it even necessary? Quizmaster reminded us that adding the uSys prefix to an object automatically hides it. Amasa gave us an interesting reason for hiding the query. Thanks to Doug for his great list of reasons and his generous list of hiding methods. Now, here’s what the reader ended up using:
object.SetHiddenAttribute(objecttype, objectname, hidden)
where objecttype equals acQuery and hidden equals True (setting the attribute to True).
Thanks for another great challenge!