I'm sure you've got a business reason for wanting to do what you suggest, but it sounds unwise to me for the following reasons.
1. Backups are there for restoring when there is catastrophic or significant data loss for one reason or another. You don't want to be playing with those files. Maybe create a copy of the backup files for download via FTP.
2. What are users going to do with the backup files? Are they going to open them locally in FMP? Will it get confusing for users because they won't be sure if they are working in the live database or in a local backup version. What if they enter new data in the local backup version thinking that they are working in the live database?
3. If they need records exported into some sort of file - why not schedule that as a Server Side script every night and place those files somewhere for your users to download. That way you are performing the export server side instead of over the WAN and the result for your users is a file that is not your database so they don't get them confused. You could place the resulting files in a container field for your users to download.
Just my thoughts for what its worth. Chris
Alright Chris...thank you very much. I'm with you 100 percent, I went on the deep-end with this one....the issue is just exporting records.
Why take the risk of missing-up the back-ups...Big Thank You for that one. Going to look at PSOS and have the export saved somewhere I can download it.
Once PSOS exports the data in excel, what is the best method to retrieve it within FM.
With MBS Plugin you can do FTP/SFTP/FTPS in FileMaker Pro/Server/Runtime.
e.g. load a file, unpack it (with other plugin functions) and process files.
The plugin can get a directory listing, too.
Thanks Christian...I was looking at FTP plug-ins for another project and was not too happy with the result. Going to look at MBS for sure...thanks.
That's what I needed, thank you for taking the time to include the code....