Much easier to setup a filemaker sync solution that supports the offline collection of information using filemaker go.
Here's half a dozen things that would work to get you on your way:
I would avoid sending data by email, as you're just giving yourself a lot more work on the other end to try and manually assemble that data back together from all of your sources.
im Prinzip geht das so:
- sichern als komprimierte Kopie in das temp-Verzeichnis
- setzen des pfades zur Kopie in eine Variable (zB $MeinPfad)
- email senden an die gewuenschten Empfaenger mit dem Anhang $MeinPfad
es gibt einen Vortrag von der FileMaker Konferenz in Salzburg ueber iOS, mit Beispielscripts
Ueber mail geht das natuerlich nur bis zu einer bestimmte Dateigroesse..
Es freut mich immer, wenn ich eine Gelegenheit habe Deutsch zu lesen/sprechen, obwohl meine Sprachkenntnisse sehr verrostet worden sind. Daher werde ich auf Englisch weiter machen.
Mike's point is well taken, and it would be nice to know what type of work is being done offline (on the mobile device). There are circumstances, however, where what you are asking about, makes perfect sense; e.g. data gathering, or otherwise just creating new records. If the mobile devices are simply gathering data that will be uploaded to the main application, creating an export of those data records, and emailing them as an attachment can be a viable alternative to a complex syncing process.
I have a federal client who does not permit the use of non-government equipment, when working in their offices. I am not even permitted to take my laptop out of the bag, when I am there. I have a timekeeping solution I use to track my time, what I'm doing, and to help prepare my invoices. So when I'm in their offices, I create records on the Go version of the solution (I'm allowed to use my iPad/iPhone, just no network connection). When I'm able to use my own computer again, I run a script that creates a .csv file of these records, and emails them to myself, I can then add them to the main application, and I'm up to date. The script then, deletes the exported records, as I do not work with them in Go, other than to meet the constraints of my client.
This is a very specific case, and may not reflect your circumstance. If you will be working with the solution, as a whole, on- and off-line, then a syncing system is probably called for. All of the links Mike provided deal with that. Syncing is a complex issue, and should that be what is really needed here, you'll need to invest the effort to understand it.
As other have mentioned, it is worth considering the option to sync data.
You might also have the option to export data use the script step to "Save a Copy" to the documents folder and then attach the copy to an outbound email.
vielen Dank für die hilfreichen Hinweise und Tipps!
Wenn wir uns in FileMaker eingelebt haben und es erprobt haben, dann wollen wir eine
Synchronisierung programmieren (lassen). Vorerst benötigen wir allerdings als kurzfristige Lösung für ein bevorstehendes Projekt die E-Mail-Variante, um die draußen erfassten Datensätze (Text, Bilder und Audio) zeitnah in unser Büro zu bekommen und zu verarbeiten.
Die Tipps werden wir auf jeden Fall ausprobieren. Danke nochmal dafür.
many thanks for your helpful instructions and tips.
When we will have been working with FileMaker for a while and will be accustomed to it, we plan to (let) program a sync-version. Initially, however, we need the e-mail-version for an upcoming project in the short term to transfer the data recorded on-site (text, pictures and audio) to our office promptly.
We will try your proposals surely. Thanks again for those.