Dialog maker applescript1/2/2024 Set the parentFolder to get data cell "ProjectDatabaseFolderParent_c" of table tableName Set the backupFolder to get data cell "BackupProjectDatabaseFolderPath" of table tableName Set the item_path to get data cell "ProjectDatabaseFolder_c" of table tableName The AppleScript executes a few processes in order as follows: set tableName to "Backup Template" that I’ve selected a source and destination folder, that there are no other FileMaker files open etc) and then perform an AppleScript that creates the. The FileMaker script that is attached to these buttons use native FileMaker script steps to check for any mandatory requirements (e.g. Both buttons perform the same script but pass in a different parameter to the script. zip backup for both the FileMaker databases and the PHP files. Getting the Path to the Source and Destination Folders zip archive of these PHP files (usually on an external hard disk) the destination folder where I wish to save a backup. the source folder containing the master PHP files that are associated with the current project (if applicable).zip archive of these into (usually on an external hard disk) the destination folder where I wish to save a backup.the source folder containing the master database file/s that I’m working on (always stored on my local hard disk).It has 4 fields that I use to store the locations to: It’s Mac only as it uses AppleScript – I do 99% of my development on the Mac platform so this makes sense for me. I use a simple FileMaker database that I duplicate for every new project that I start – the link to download this is below. I go to great effort to ensure that files I’m working on for my clients have never crashed before they are deployed into production – if FileMaker Pro Advanced did crash whilst I had any client files open I simply trash them and revert to the previous backup I had made. I also like to confirm that the files that I’m about to copy into a. I’ve also learnt the hard way too – there’s nothing worse than having to re-do a major chunk of work because FileMaker crashes, you accidentally click cancel instead of OK, there’s a blackout and you haven’t got a UPS etc etc. I’ve been working this way for so long now (over 10 years from memory) that it’s become a habit for me. Whilst I’m developing I like to close my files periodically (usually every 20-30 minutes or after a major chunk of work has been done) and make a quick. I use a mix of backup plans to keep known good copies of my files locally as well as off-site (this post doesn’t go into the details of what constitutes a comprehensive backup plan). I’ve traditionally developed using locally stored files except for my CWP/PHP work and have used a companion database for each new project that I start that I use to create compressed timestamped backup archives of my master database file/s and any associated php files. I develop on locally stored files as well as files hosted by FileMaker Server (I do a lot of FileMaker Custom Web publishing work using the FileMaker PHP API which requires the files to be hosted by FileMaker Server). All FileMaker developers have their own habits about how they develop, what tools they prefer to use and how they setup their working folders and backups.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |