tag:blogger.com,1999:blog-8480357.post2955095002487095675..comments2023-03-27T06:02:03.105-04:00Comments on Maureen's blog: private in desktop viewsMaureenhttp://www.blogger.com/profile/08783404920615182265noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8480357.post-34801095455549759212007-06-27T21:53:00.000-04:002007-06-27T21:53:00.000-04:00what john said :-)what john said :-)Neil Wainwrighthttps://www.blogger.com/profile/15717915927958472446noreply@blogger.comtag:blogger.com,1999:blog-8480357.post-24060778355347016992007-06-27T12:57:00.000-04:002007-06-27T12:57:00.000-04:00I agree with Andre ... as long as we can build and...I agree with Andre ... as long as we can build and edit Private on First Use views in designer, then I think your ok.<BR/><BR/>Now, talking about PoFU views ... any way you guys can give us a way to force an update of private views, created when the user opened the PoFU view, without having to resort to Database Script or Action button code that forces all those private views to be deleted and recreated the next time the user opens the view? That creates a nightmere if users never leave that viewUnknownhttps://www.blogger.com/profile/16995240613896001246noreply@blogger.comtag:blogger.com,1999:blog-8480357.post-58650370975956568392007-06-27T11:02:00.000-04:002007-06-27T11:02:00.000-04:00So long as we can still do "Private on first use" ...So long as we can still do "Private on first use" in Designer. Though even that is sort of obsolete, in my opinion, when you could have a view that uses @SetViewInfo to automatically limit itself to the user's category.Anonymousnoreply@blogger.com