I thought I'd replace hand-written code I got from Mark Mitchenall many years ago, since 4D had since come out with two commands (since 15.4?) which theoretically, would make that code unnecessary -- blob to users and users to blob.
From what I understood, the users, groups, and modifications made by the Administrator user would be deleted and replaced upon execution of blob to users. Great! I could create a routine which would export those changes when bringing down the server, and import them when starting the server! Well, as it turns out, for some reason, the modifications (membership) changes made by my Administrator changes are not all being retained. I tried this two different ways, too: First, by executing blob to users in 4D local mode, when signing in as Designer on my development and production machines. This way, when I built the resulting compiled structure, it would be up-to-date already. The second way, was as I described above, by simply executing blob to users in the "on 4D Server Startup" method. Neither method retained my change. To test this, I logged in as Administrator and simply changed one membership status of a person added by the Administrator. The Groups were all added by the Designer user, since I don't want these particular groups to ever disappear. Does it matter that the groups were created by the Designer? The way the documentation reads, any group "created or modified by the administrator" should be affected. I am using the latest hotfix of 17.3. Where did I go wrong? Thanks, Doug ********************************************************************** 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] **********************************************************************
