Jump to content

drums31

Members
  • Posts

    13
  • Joined

  • Last visited

About drums31

  • Birthday 01/16/1964

drums31's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Hey Fenton. Thanks for your time and detail on this issue. Wow, I'm finding more and more things I never knew about FM. I should remove the Advance from my skill level. I've messed with just about all of the export types but the web related ones. I tried this, but I'm sure I missing something. I've attached the error message to an e-mail. Please take a look if you have time. Platforms... It is necessary have this work for both Mac & Win. Thanks!!!
  2. Hi Amy. I'll try to cover things together without getting fancy. You've indicated that you have a Serial ID. That's good providing the field is set to have a unique value (define fields). When you import from another file, it's best to find only the records you intend to import, simply eliminating unwanted records. Nonetheless, when importing, select "Update matching records in current found set", then check "Add remaining records". Duplicates are easy to find... Browse, find, click in the field of choice, e.g. Serial ID, enter "!". This will reveal records with duplicate Serial ID's. Now to determine the imported records -vs- original. There are several ways to do this. Another good habit is to include creation and modification dates (define fields). Of course, both files must have these date fields to allow importation of the value. Obviously, you can only perform this in a single calendar day. AHHH, but to make sure the exporting file has todays date on all records, you need to create a simple text field that you can update all intended records. Basically flagging the records. You may elect to format the text field to inlude a single value checkbox. Steps: 1) Find the records you want to flag or simply show all records 2) Cursor to the new text field or checkbox and enter a character or check to box 3) Choose "Replace" 4) varify the number of records to replace and go for it This will add the value to all intended records and update the modification date at the same time, so when you've completed your importation, you can separate the records by modification date. You should check a couple of records in the working file to varify the change before importing to the original file. Another way, perhaps even easier, is to simply create the same text field in both files and before each import, replace the character in the found set of records (flagging). After you import these records into the original or master file, you can find this character in the same field, which will identify your newly imported records. Be careful with the "Replace" function. Make sure you're in the intended field, or you may loose data. It's best to duplicate the working file before you "Replace" any data. Good luck, Steve
  3. Hey Lee. I took your advise and exported tab-delimited, which of course eliminated the commas and the quotations as "comment" states. After that, it kind of simplified things by replacing tabs with ^'s. Incidentally Lee, after "comment's" find and replace function of t, I tried , and replaced with ^. It worked equally well, but then I had to find " and replace with nothing to remove them. I just wish there was a way I could export with ^, as I cannot expect users or administrators to conduct this conversion, but as I've mentioned, I will try validating the tab-delimited file first. Who knows, it just might work out. Anyway, both of your suggestions have helped me immensely. Thank you for all your help!
  4. Worked great thank you so much!!! Is the ^ Character used only to identify the tab or space between fields, or is there some language significance? I'm wondering if the validation tool requires this separator. If not, two thumbs way up!
  5. Thanks for the tips Lee. I've downloaded the TextWrangler and started to mess with it. Following your steps, I haven't quite figured out how to replace yet, but I'll get it. Interestingly, via the Special Character menu, I rediscovered the separator character "^" is a "Circumflex Accent". Thanks so much for your time on this strange issue.
  6. Sorry, I didn't clarify the time separator thing. Not related to the exporting and conversion of the ^ separator issue. This is just one nagging issue I have had with FM. The users of my file(s) complain on occation that they have to manually enter colon ( time separators when entering a time. That's all-- sorry for the confusion.
  7. The samples in Post#171128, were only a few of the many fields that are exported via the .bas (Basic Language source code file) selected from the FM export file type options. So yes, all data exported from the 126 fields needs the ^ separators instead of commas and quotations. Gotta run, i'll check back early afternoon. Thanks again Lee.
  8. Hi again Lee. YES, I am exporting data from 126 fields then runnung the .txt file through a validation program by FEMA. Is there a way to export a .txt file directly, or will I have to continue to change the .bas to .txt? I'm not sure whether the validator will accept a basic file. Thanks for the calc, but I tried it with the "Start Date" and did not get the proper result. Incidentally, Of the 126 fields, there are three dates to convert... - Start Date - Arrival Date - Return Date Oh, I have another little issue with FM. Formatting a time with ":" separators will not auto enter the separators-- They must be entered manually. It can be stamped, but the times are never entered during real-time. Hmmm... Thanks!!!
  9. Hi Lee, Thanks for the reponse. I'm not exactly sure what to do with your calculation. Should this be the first field to be exported? Steve
  10. I am in need of having "," data separators converted to "^" and without quotations. Sample (1)... data exported using .bas 28017,"NY","01/01/2004",400003,"0","1000",,,"5.0 Sample (2)... data needed for validation tool (win) using .txt 28017^NY^20040101^400003^0^1000^^^5.0^ Forgive me, but I have forgotten the term for the character or separator "^". The date format is easy to modify and achieve the same result, but I don't have a clue how to accomplish the conversion of separators. Thoughts are deeply appreciated.[color:brown]
  11. The date fields often get overlooked due to the incident volume. I really need to offer a transparent entry. I will try the seconds conversion. Calc 2 looks cool too. Thanks
  12. Hey, thanks LaRetta and Fenton for your posts. I should probably use my name instead of a screen name. I was a subscriber to this forum years ago. As you can tell by my bio list, I'm pretty busy. LaRetta, Unfortunately, the use of this file will not support a time or date stamp, as the actual entry time of incidents may not during the incident. I like the Result of Time calc though, I will look into that-- although, I have formulas for all elapse times already in place. Fenton, Yes, The file needs an "end date". I'm all set with elapse times. It seems as though somewhere I need to reference a julian date or "day of year". I have already created a Julian date field, which I think should be the result + the hour differencial from an if statement. I'm equally thinking, i may have to create some additional calc fields to reference beyond a 24:00 field. My heads swirling with concepts, but I just cannot nail it. Hoping for some light!
  13. I have an incident records file that requires times and dates of the following: - start time - en-route time - arrival time - end time Each time value is manually entered, and the incident date is auto entered as the creation date (modification allowed). I am having difficulty with a calculation to apply into a calc field with a resulting date value, the correct DATE to each time (e.g. start-time date, enroute-time date, etc). Senario Event: As the en-route-time, arrival-time or end-time may advance into the next calendar day or julian date from the start-time (using 24:00 time), the date needs to advance as well. I've tried to compare each time to the start-time by referencing "< start-time", as the time into a new day would usually have an earlier clock time, but I have not been successful as these times may cross days and have a greater time value. Additionally however, in the unusual events that the end-time is > 24:00:00 from the start-time (even spanning several days), the date would need to advance as well. Any thoughts?
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.