Filemaker can import XML data - provided the data is either in Filemaker's FMPXMLRESULT grammar, or that you point it to a XSLT stylesheeet that tranforms the data to FMPXMLRESULT grammar.
Thanks for your response.
We have converted the data to the correct grammar and all works well with a test Filemaker database but because the inbuilt Filemaker scripting is disabled and the File -> Import Records menu item is also disabled we can not get the data into the third party job tracking system that we use.
Any ideas on how we can get this data into the third party system would be greatly appreciated.
If you don't have the privileges to import, you'll need to talk to the person who developed the solution.
We have and they are very clear that they will neither allow us to use Filemaker scripting, the import function or create a ODBC/JDBC connection. This is the main issue and the reason I am trying to find a workaround.
Again, any advice would be very much appreciated.
I don't see a way around this (not a legal one, at any rate). The developer controls what users can do through Accounts and Privileges. If they don't want you to import, you cannot import.
Thanks again for your input. While I still don't have a solution, it's great to know there's people who are kind enough to help.
Now back to the task at hand...
Is there a macro style approach that I could look into? E.g. Record the actions performed on the page and have the macro (or similar) set-up so that the data completed in the page is as per an XML file.
I would be happy to use a utility or application that would provide the ability to do this. Does anybody know of such a tool?
Another option you could try is to create your own file. Then put a table occurrence on the graph of the external file, using whatever your access account is. If you have enough permissions in that file to create records, you may be able to do what you want from your own file, where you can create scripts, and even layouts based on the external file.* Access to create a new records is quite different from Import, and you may very well be able to do it.
If you import your data into this file, you should be able to automate creating matching records in the external file, and populating the fields. More tedious than Import, yes, but once done it will perform much the same.
*Once you have table occurrences of an external file in your file, you can create pretty much whatever interface solutions which you have permission to perform; which may be quite a lot.
That's an excellent idea, and should be a lot easier to implement than some generic GUI scripting utility. Provided, of course, they know their own password.