MHAriete64 Posted August 7, 2007 Posted August 7, 2007 I'm getting a flat file from an MIS department and I need to update my solution's information with any new information. I've decided to import each record into an "imported data" field then parse it and set it into its appropriate fields, then do a "compare records" to update my existing data. My problem is in the parsing of the data. I can direct how I'll receive the data (i.e. csv, tab-sep) and the order of the fields. But, I cannot direct how many words will be between each separator. Does anyone have a good recommendation for moving through a field of data (of no pre-set field length or characters)? I tried LeftWords, but some fields have multiple words. If I use Position and set the search string, what's the command to "grab" or "get" the text between these searched characters? MiddleWords seems to fail me. Also, if someone has a better idea to my flat file dilemma, I'm all ears. Thanks.
Vaughan Posted August 7, 2007 Posted August 7, 2007 It'd be easier keeping the data in separate fields, then compare the fields to the main table.
MHAriete64 Posted August 7, 2007 Author Posted August 7, 2007 Yes, I agree. But, I'll get it as a flat file. I noticed in another thread someone discussed parsing and setting the information into the appropriate fields during import. Maybe I'm a bit too novice to have that figured out. I agree, that would save a step, but I still have to parse on import, no? Thanks for your interest.
Vaughan Posted August 7, 2007 Posted August 7, 2007 I must be confused as to what you mean by "flat file". A flat file usually contains fields and records. There are delimiters between fields (commas or tabs) and delimiters between records (carriage returns). When FMP imports a file it'll put it into fields and records automatically. What is it that you're getting?
MHAriete64 Posted August 7, 2007 Author Posted August 7, 2007 Oh the lessons we learn the hard way. I was under the impression that my flat file would have comma separators but that FileMaker wouldn't see them. DUH! I've spent way too many hours trying to figure out how to parse the data into fields. Feeling very silly at this point. Please feel free to disregard this thread. And, thanks for your reply.
Recommended Posts
This topic is 6318 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now