I have found that if you take a 4D v17r5 program and convert it to v18. Then change the database to a project database it will lose the memberships in the users and groups. When exported you will see all your groups and users. But the memberships between the two will disappear. With the exception being “Designer” and “Administrator”.
Even worse. If you took a User to blob file saved in 4D v17r5 and import it into v18 it will corrupt the minimal users and groups file created when the database was converted. Effectively all the groups will disappear and corrupt groups groups will come into existance. A curiosity is that the designer and administrator will keep their memberships, but all the other users will lose the relationships. I have noticed the the new directory.json no longer has user numbers. I suspect this may be part of the problem. This is certainly causing issues with my linking users to their [Employee] table records. The user number used to be a constant and I would use it to tie a user to an employee record with a simple Longint. Can anybody verify this is true or not. Or is there something really simple that I am missing. The good thing is that my users and groups are pretty small so I can manually recreate the directory.json file. Then make a backup of the file in my v18 project. I am using the method of saving the directory.json file in the dat folder to keep my users and groups constant between versions of the database. I remember there was a discussion about users and groups in the past and issues with import-export of the data to a blob. ********************************************************************** 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] **********************************************************************
