all I need is to read the content of a text file into a text field and I can’t figure out how.
Situation: I have ≈150’000 folders, each with one image file and one xml/text file with meta information about the image file. The image file and the meta data need to go into the same record.
I’ve looked for hours now, but couldn’t find a solution:
• I can’t use the import folder command, because it creates new records for each file in a directory.
• I can’t use Do AppleScript > do shell script > cat x.txt, because I can’t get the result into FileMaker.
• I can’t use the new Read File script step of FM18, because the solution is on FM16 and FM17. (I tried it nevertheless, but all I got was the filename!?)
• I’cant use a plugin (MBS would work just fine, I think).
So, what are my options? Any ideas?
I would love to insert the xml file into a container and then read the container raw data — but how? A couple of years ago, I have read about someone actually doing this, but I can’t remember where or how. That would be cool!
Any other suggestions?
Thanks so much!
there is a price list in Excel with images embedded. Do you have an idea how to import those records into DB with corresponding images preserved?
Note that I've attached only two records, there are 600 of them. Any manual manipulations with the images is not an option.
I am trying to import data from a MySQL database and need to somehow also import fieldnames to be the fieldname in FMP. Is there anyway to do that? I have a CSV of the fieldnames and I also have a MySQL dump of fieldnames and associated data.
Thanks for any help.
I have searched the forum and internet and not found an answer to my delima.
I have a solution with a scripted import of a csv file. I do not want import dialog (e.g. mapping), so I have it set to no. I don't know the name of the file, only that it is a csv file. If I leave the filename out of the import dialogue, the default SHOW filetype in the open file dialog is for a filemaker database. The user needs education to change the SHOW to csv or all. That is undesirable. If I import a correct file once, the next time the script runs in that session, it prompts for a csv file, but if I quit the application and run it again, it goes back to SHOWing filemaker databases. If I provide a bogus file, e.g. YourFile.csv -- I have to capture errors or I get no file dialog for them to find their file. If they cancel, they get a filemaker dialog I don't control that tells them the user aborted the import, continue or cancel. If they cancel, the script exits and I don't get control. That, too, is undesirable.
What is the best practice for scripted imports so that whether the user complies or cancels, I maintain control of what happens next?
Who Viewed the Topic1 member has viewed this topic:mr_vodka