October 7, 200520 yr Hi all, I'm using the "Invisible Layout Objects" technique to hide some of my objects. It basaically use a portal and hides the objects based on a relationship. My issue is that this technique is not working in Find mode. It displays all the objects that are suppose to be hidden. I'm wondering if someone has found a a fix or work-around for this issue I'm having. I believe I have a work-around but it would probably take much work Thanks!
October 7, 200520 yr Hi Sledg, You are not wrong there!. I have just started using the same 'invisible' method and hadn't yet realised the problem but I just checked and yes! they do show up in find mode. How about scripting to go to a copy of the layout in question (but with the said portals removed) before entering find mode?. Shouldn't be too much extra work Phil
October 7, 200520 yr Author Hi Phil, I wish it could be that easy (if I understand what you are saying correctly). The problem is the layout is dynamically built based on relationships. The relationship works like this; if a field is empty on a different layout then don't show a group of objects. Think of it more as a preference setting. So it's constantly changing based on some settings. Thanks! Edited October 7, 200520 yr by Guest
October 21, 200520 yr Author Hi again, Well, I had to work around the problem to get it working the way I wanted it to. I basically recreated the find mode by using browse mode. That way I can still use the "Invisible Layout Objects" technique. To make a long story short; I duplicated the table that I was going to perform the find on. The user would enter the find data in the duplicated table. A script would then store all the data in a field. I would then go to the original layout and use the data to perform the find. It actually worked out well because I used the data I collected to store the user's search criteria. That's the short story. I actually did more because I recreated the omit and multiple search functionality on the status bar (since I hide it).
Create an account or sign in to comment