Hi All, I’m asking this because I have time scheduled tomorrow to try this approach. But I though I’d explained and see what others have experienced using similar approaches.
So if I want to protect the db from a user getting into “design mode” - given we have rolled our own password security - can I simply do the following: Add a 4D Group in the password editor. Is there not a checkbox to disallow a user into design? So if I set things up this way and then… After the user logins to our custom PW login system immediately identify them as a member of this group will that work? Will that keep them from getting access? Thanks, John... > 4D v12 Windows clients > > I have read all the threads in the Nug concerning this and can’t seem to find > a solution. > > I have been trying to figure out how to disable the close button on Splash > screen windows v12. Not the main Application window (that works). > > If I use the command “gui_DisableCloseBox(windowHandle)” from Win32API it > does disable the close button of the application window but not the splash > screen. > > I need the Splash screen to also have a disable close button. > > Why would I want to do that? because the client WANTS the splash screen and > keeps it maximized. > > Is there any straight-forward way using Win32API? > > Thanks, > John… > ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************