Hi Nick,
I use filemaker as well to post database changes. A calculation field in filemaker combines all the fields for each record into the summaryexport field I have in my db database(make sure they are in exactly the same order as your .cfg file), separated by the pipe delimiter, such as:
=field1&"|"&field2&"|"&field3&"|" etc. . .
Then, a looping script copies the contents of the summary export field in each record to an export field (global).
Another script performs the export to the default.db (or whatever your .db file is named).
Once done, it's a simple matter of uploading and replacing your .db file. (I have a FM plugin that ftp's it directly so I don't need to do this step) That same plugin imports the information as well and updates the Filemaker Database.
My particular database is pseudo realtime. Whenever filemaker receives an email of a modified record, a script is triggered that downloads the .db file, updates the inventory information and reuploads a modified .db file.
Hope this helps.
I use filemaker as well to post database changes. A calculation field in filemaker combines all the fields for each record into the summaryexport field I have in my db database(make sure they are in exactly the same order as your .cfg file), separated by the pipe delimiter, such as:
=field1&"|"&field2&"|"&field3&"|" etc. . .
Then, a looping script copies the contents of the summary export field in each record to an export field (global).
Another script performs the export to the default.db (or whatever your .db file is named).
Once done, it's a simple matter of uploading and replacing your .db file. (I have a FM plugin that ftp's it directly so I don't need to do this step) That same plugin imports the information as well and updates the Filemaker Database.
My particular database is pseudo realtime. Whenever filemaker receives an email of a modified record, a script is triggered that downloads the .db file, updates the inventory information and reuploads a modified .db file.
Hope this helps.
