It may be the "standard practice" but it's not a location for the run time solution folder that works well. The runtime folder contains both the executable and the database file(s) it is designed to open. Putting this runtime folder in the program Files folder is like creating an MS Word file and then putting it in Program files alongside the MS Word Executable.
I recommend that you specify a different location for the runtime solution folder.
Well what about on the Mac? It's happening there, too. Should it not go in /Applications like everything else?
The problem with installing outside the standard folder is that then every user has to install their own copy.
Again, I never had this problem prior to FM11, so there's gotta be something that changed or some way to make this work. I still have old versions of my runtime that I made with FM10 that install to Program Files without any issues at all.
I don't own a Mac, but would not be suprised to see a similar situation.
Simply installing the solution folder directly to the drive, outside of the program files folder should make it accessible to all users, but I agree that this doesn't necessarily make it easy for your users to find the correct file inside that folder to use to launch the application.
I would try installing a shortcut or alias to the executable from the solution folder into Program files or to the users' desktop folder as a way to make the solution easily accessible to each user. There's an "All Users" folder for that purpose on my Windows machine.
I appreciate your feedback, and I'll play around with this, but I still think there's gotta be some way to make this work without that sort of a work-around.
Again, I never had this issue prior to FM11, and if you download one of my previous versions of my solution and install it to Program Files the permissions error does not happen. Worked just fine on both Windows and Mac. It only happens on my versions created with FM11 or FM12.