> So what’s the recommendation on giving startup progress so they know that the > server hasn’t frozen at some point during the startup method?
To the best of my knowledge, we do not recommend any sort of UI on the server. So, it is hard to make a recommendation for something we don’t recommend. Trying to help even though we don’t recommend a UI on the server - If this was on a client or standalone I would suggest the Progress component: http://doc.4d.com/4Dv15/4D/15/Progress-New.301-2399698.en.html http://doc.4d.com/4Dv15/4D/15/Progress-SET-TITLE.301-2399709.en.html http://doc.4d.com/4Dv15/4D/15/Progress-QUIT.301-2399699.en.html C_LONGINT($vlProg) $vlProg:=Progress New Progress SET TITLE($vlProg;"Title of window for doing stuff 1";-1;"description of stuff being done") // do stuff 1 Progress SET TITLE($vlProg;"Title of window for doing stuff 2";-1;"description of stuff being done") // do stuff 1 Progress QUIT($vlProg) However, I don’t think that using the progress component would be appropriate for the server because it is still a UI and in general our documentation suggests against any sort of UI on the server.. Regarding notifying the administrator about ongoing startup tasks - what about using the DISPLAY NOTIFICATION command? http://doc.4d.com/4Dv15/4D/15.6/DISPLAY-NOTIFICATION.301-3818361.en.html -Tim ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
