If it is a one time important you want to bring the entire text of the file into one record, you can select the text in the file, copy it and paste it into a text field in FileMaker.
Sorry, I sent the wrong reply first.
Could you provide a little more information?
Is it a one time import (my previous response) or is it a repeating process? How frequent?
Are you adding the text to an existing record everytime, a new record or a mix?
It will be a repeating operation.
each time I need to import the content of one new text file into a new record of a specific table field.
Supposing you accomplish this; what happens next?
Is this data split into records or used in some other way?
Can you tell us what kind of data this represents?
New orders? A list of new contacts? Price updates? ???
What is the size of this text file?
One reason I ask is that you could conceivably import the data into a utility table.
When done this way,each line from the text file becomes a record in the utility table.
The records from the utility table could be placed in your text field easily, by a number of methods.
And then the records in this utility table would be deleted.
here is a file that does what you ask, and more. There are no instructions, so play with it, study it.
My apologies, I replaced the file, because it had an error with appending data.
Import Any File_4A.fmp12.zip 152.6 K
If the text file is encoded as UTF-8 (or ASCII can be treated as UTF-8), "insert from URL" to text field will work. (CRLF is inserted as is then become 2 line breaks)
Otherwise, you need converting encoding in some other ways.
this is my suggestion as well. If you really really want the "file" pushed to one field (as TEXT), the
Insert from URL
is the step to take.
YMMV if the file is not text-based, of course. Insert (into a container) just puts the file "as-is" into a storage for later export or preview, but cannot be "parsed" from there directly. And that's why Bruce is asking for more thoughts on what and why.
Thanks for the tip on using a container field. I needed this now as I was getting a text file with local zip codes from a web site via Insert from URL.
The text file was ANSI encoded, but contained extended characters.
Inserting into a text file messed up these characters, but using a container field preserved them for later exporting and regular import.
Amended: TEXT files are perfectly acceptable to be put into container fields! There are some new functions in FM16 that help with text/container. These were not announced when the post in JAN of this year was made.
TEXT content can also be put into containers, made easier with these functions!