Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

AlanP's Achievements

Community Regular

Community Regular (8/14)

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

Recent Badges



  1. AlanP

    Modifying Tooltips

    Thank you! hahaha it was collapsed...now I feel silly Appreciate the help!
  2. Sorry for such a basic question, but we recently upgraded from FMP9 to FMP13. Existing databases were converted. I need to modify tooltips...but apparently it has changed drastically (at least for me) with FMP Advanced 13. Silly question? How do you edit existing tooltips? I can't find the option ANYWHERE. The FMP advanced manual provides no guidance and just a vague statement that you can edit tooltips. I've been able to "show" which fields have tooltips, but nothing else. Right mouse clicking, looking in layout, format, etc., menu options doesn't show anything. Inspector doesn't show any options. Thank you!
  3. Ah ok. Could you recommend what I should put for the calculation? I'm not sure how to use the SerialIncrement() function.
  4. Would that be better to use? I'm not very familiar with that function.
  5. Good morning all, I have to do an import of data into FMP, but the field we are 'matching' to is configured differently than FMP. EmployeeID from the CSV file we are importing is a 6 character field, where the employee ID itself is actually 4 or 5 characters and any remaining empty values are prefixed with a 0. Such as a 4 digit employee ID is shown as 001234 and a 5 digit employee ID is shown as 012345. In our FMP database, the EmployeID is shown without any prefixed 0's. So it is 1234 or 12345. When importing, these don't match up. I'd like to make a calculation in FMP called EmployeeIDConverted where if the EmployeeID in FMP is a 4 digits, it displays as 00xxxx (prefixed with two 0's) and if 5 digits, it displays as 0xxxxx (prefixed with one 0), so I can successfully match records for import. I'm not exactly sure how to do this (tried a few ways, but didn't work). Thank you in advance!
  6. I have given up on this question, thank you anyways.
  7. Can PatternCount, in Case, have more than one variable.
  8. Thanks Comment! Wow...I did say that originally! I'm all over the place with this script requirements. But it works perfectly, thank you so much for all your time and assistance on this! It is greatly appreciated!
  9. Had another question, When the script executes, the alpha's start at 1 instead of 0 So it should look like A0, A1, A2, A3, A4, A5, A6, A7, A8, A9, B0, B1, B2, B3, B4, B5, B6, B7, B8, B9, etc. However it's skipping the 0 (e.g. A0) and going straight to 1 (e.g. A1). Also saw this on the numbers as well, it will start off with 01, 02, 03, 04, etc. instead of starting off with 00, 01, 02, 03, 04, etc. (that being said the numerics work fine for everything else...e.g. in the teens such as going to 10, 20, 30, etc., so 0's appear there).
  10. That worked perfectly! Thank you!!! :
  11. Hopefully this is an easy fix! END GOAL: Two separate date fields (one is imported) need to match. If match, the calc will say 'MATCH', if not it will be blank. PROBLEM: The imported dates come from a SQL database from somewhere else and don't have a leading zero (0) for the month, whereas in filemaker it does include a leading 0 (e.g. 01 compared to 1) CALC: This is what I have so far, and it works fine on 2 character months, but won't on the ones without leading 0's. Any ways to fix this issue? Case ( Imported_CertDate_MOPR = Training History::Training Date History;"MATCH" ) "Imported_CertDate_MOPR" is the imported dates that DO NOT have the leading 0's for 1 character months. "Training Date History" is the FileMaker db dates that do have the leading 0's. I'd prefer not to muck with our data at all. Thank you in advance!!
  12. I could cry right now...THANK YOU BOTH!!! Yes, that is exactly what I need! How do you guys know all this stuff?!?! :
  13. It's hard to explain. Basically we have specified serial numbers to enter into the database, lots of them, that have a particular structure and sequence. The ABC1234 was just an example, because eventually it would be ABC1235, ABC1236, or even AAA1111, etc. it's almost like a prefix. The suffix to it would be the one that changes (these are "blocks" of serial numbers). So ABC1234A1, ABC1234A2, ABC1234A3, ABC1234A4, ABC1234A5, ABC1234A6, ABC1234A7, ABC12234A7, ABC1234A8, ABC1234A9, Then it goes to the next prefix, ABC1234B1, etc....all the way through Z9 prefix. Then the 'block' of serial numbers end. Because there is so many, it's hard to enter them all in manually. The user needs to specify the prefix (such as ABC1234) then allow the script to do A1 all the way through Z9. Does that make it clearer or as clear as mud? ;-) It's harder to write out than actually show. Oh, and the other comment. I was just saying I don't mind if there is TWO scripts. (one for A1 through Z9, and another for the straight numeric prefixes of 01 through 99).
  14. Hi everyone, I'm a little lost on even how to begin doing this. here is what I need to do: - Need to add to a table (using a script) a 'block' of serial numbers. - Serial numbers follow a standard convention, only the last two characters change (i.e.: ABC123456, ABC123457, ABC123458 or ABC1234A1, ABC1234A2, etc.) Also on the alphas, it ends at 9 and restarts, eg.: ABC1234A9, next up would be ABC1234B1, etc.) - I don't mind breaking up entering straight numbers (at the end) vs alphanumerics at the end. - All must end at the final position. For example, Alphanumerics end at "Z9", numerics end at "99". So...ABC123401 through ABC123499 Alphanumerics: ABC1234A1 through ABC1234Z9 (but in 9 incriments at the last character). Any ideas on how to go about doing this? The user would have to specify the first 7 characters of the serial number (it changes based on what they need to add to the database). THANK YOU VERY MUCH!!!!
  • Create New...

Important Information

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