Jump to content

This topic is 5377 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

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 by Guest
Posted

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

This topic is 5377 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.