Thanks for your replies to this. I will experiment with signing BUT I really don't think this is the issue, for 2 reasons:
1. I've had this problem since before Gatekeeper was invented. 2. I'm familiar with the Gatekeeper dialogs and this isn't one of them. Gatekeeper would normally prevent the app being opened, but this can be bypassed by right-clicking the app and selecting 'open'. That's not the problem here. This does seem to be some weird permission scenario but I can't get to the bottom of it. Details of any other successful runtime installations would be helpful - especially where problems have been found and overcome. Finally, you are right that the app ought to be a good candidate for using a default data file, but unfortunately the previous developer built some code that required the use of the data file as a temporary store for building certain reports. It's annoying, but I don't have time to unpick all that stuff! So, for now, the data file will have to stay outside the app. Thanks! -- Sent from: http://4d.1045681.n5.nabble.com/4D-Tech-f1376241.html ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
