May 14, 201015 yr Hello, I have a runtime solution that is designed to grab the PC's Username and use that as the Primary user account for the solution. On first launch after installation the FileMaker run-time solution runs a Script which grabs the Username and creates an Account based on a pre-defined privilege set. This process works fine on Windows XP and Windows 7 version. But when I run the Mac OS X run-time version it fails to create the Account. The Script is running with Full Access Privileges. I know this has something to do with the OS level permissions but I cannot find a common pattern here. Any suggestions? Best Regards, FMBiz.net Edited May 14, 201015 yr by Guest
May 15, 201015 yr Author Hello FM Developers, I have figured this one out...finally. My Installer Package was not properly setting the Permissions to the bundled Folder and SubFolders. Everytime I would package the solution and install it, the Solution file would become Read Only. I had to start using PackageMaker to see this level of detail, but works great! Thanks, FMBiz.net
Create an account or sign in to comment