Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Title
    Database Administrator
  • Industry
  • Gender
  • Location
    Columbus, NE
  • Interests
    Flying ultralights and amateur radio

FileMaker Experience

  • Skill Level
  • FM Application

Platform Environment

  • OS Platform
  • OS Version

FileMaker Partner

  • Certification
    Not Certified

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

WF7A's Achievements

  1. Thanks for the great input--I'll take you up on it. I was using names as keys because the original coder didn't create unique key fields; I've added them. (FMP does that automatically now when tables are created--a VERY good thing.) The "problem" with color-assigned text went away after I talked to one of the department heads: they were planning to make the aforementioned lists, then print them on a black and white printer; I then commented that color text in black and white printouts is a bad idea, so I'll affix footnoted asterisks to the specific names--that's much easier to do calculation-wise. Thanks again.
  2. Sorry 'bout that--here's the section of the relationship graph that I'm working on. (I know you'd rather have the database uploaded here for examination, but I signed an NDA so I don't think it would be proper to post it here.). ...and I apologize for the wrong nomenclature--they're not grandchild tables, but a table related to the child tables. As for the purpose, it's so managers can see which individuals belong to a specific department of an organization; if they do, the name should be highlighted in red. The original list is in an Excel spreadsheet, but I have some latitude as to how it can appear in FMP. ...and sure, it can be scripted. (I wouldn't ask for someone to script it for me, but if I had some guidance I could wing it.)
  3. Greetings, all. This one's tricky: I'm using the List function in a parent table ("PARENT") field to create a comma-delimited list from a child table ("ESU7_DEPT_CONTACT_EARLY_CHILDHOOD" ) using this command: Substitute ( List ( ESU7_DEPT_CONTACT_EARLY_CHILDHOOD::NameFL__lxt ) ; "¶" ; ", " ) It dutifully lists all names from the child table, separated by a comma. However, I'd like the child table names--that are related to grandchildren tables--to be highlighted in red in the aforementioned List function so the output would look like this: John Smith, Jane Doe, A Blivet, Al Capone, Gomez Addams Is that doable? TIA for your help. Rich
  4. Thanks again, and that's a good point about sorting through all the records in table; I'll have to re-evaluate the solution before I put my foot in it.
  5. Howdy, howdy: I found a neat way of performing a sort within a portal (in the attached file), but I'm stuck trying to amend one of its scripts' steps: in the setPortal_refresh [field] script, line 7, it has: ExecuteSQL( "SELECT ID from Contacts WHERE State = ? ORDER BY " & $field & Case ( $$sort_desc; " DESC" ); ""; ""; States::abbreviation ) The thing is, I want to exclude referencing a state--I just want to be able to sort each column's contents, state notwithstanding. I tried removing the WHERE part of the code but I'm just not getting the syntax right. How would I tweak the syntax to accomplish my goal...or by tweaking the syntax it would cause the portal sort script to fail? As always, TIA for your help. Cheers, Rich Portal_sort_fast12.fmp12.zip
  6. I created a workaround--I created a new table, loaded each image into its own record in the new table, then used the caption name field in each table to tie the tables together.
  7. This is weird: I have three .png's I want stored in a global container field, so I created the field--set for three repetitions--and inserted a .png in each "slot" using Insert Picture (when I right-click on the field.) They insert fine and referenced calculations associated with the field work as they should while I'm connected to the file. (It's hosted on virtualized FM server.) However, after I exit the file and re-enter it, the images are missing from the container field as well as from the referenced calculation fields. As a troubleshooting step, I created three separately-named global container fields and inserted the appropriate image in each. Same thing: leave/exit the file and the images disappear. Because it's a global field, I can't store the images externally. Would could be causing a container storage problem like this? I'm using FMP and FileMaker Server
  8. Sorry about that--I should've written "Cartesian Product Relationship"; I do have the "X" selected between tables but used the ID as the connecting fields...which is moot because if I recall correctly, one can use any two (connecting) fields in such a relationship; it doesn't have to be the ID field. "I am afraid I did not understand the "default" filter thing. If you have a predicate that you want to apply always, regardless of other conditions, why don't you implement it as part of the relationship?" Simple answer: because I didn't think of it. : | Thanks for the suggested fix (it works well), and I'll post separately about the script triggers...and sorry about posting picture instead of code--I won't make that mistake again.
  9. Howdy, howdy: I have a self-join portal (by recordID) with five global fields above it that I want to use as filters, with the "default" filter being EVENT_PARENT_X_ID::EventDate__lxd ≥ Get ( CurrentDate ) so that if no values are chosen as filters, the portal will display the records with the current date, forward. The problem is how to set up the filter calculation so that if one or more filters have values chosen, the portal will filter records based on those values. The problem is--at least how I'm looking at it currently--is that I'd need to create many permutations for the filter calc to cover all conditions. Surely, there has to be a better way of coding this! Also, here's an odd thing: I attached a script trigger to each of the five filter fields so that when the value within is changed/modified, it fires the script to flush cached join and external data and refresh the window. The weird thing is, that none of the script trigger options will fire the script, but when I manually fire the script, it works as it should.
  10. Thank you both. It's a personal preference thing, though: I'm/we're used to seeing people's names in ascending order vertically, not horizontally (when using "Across First"); it's a little like visual ping pong. It's times like these where I wish FMP was more robust when it comes to document formatting. *wistful sigh*
  11. Howdy, howdy: I'm curious if there's a cheat where FMP will create reports where the sub-summary sections can run the width of a page but the Body section would print in columns; it would make some of my reports much more visually pleasing. TIA for your help, Rich
  12. Thanks for the file and follow-up--I appreciate it!
  13. Thanks. I didn't think it would be too complicated, but elsewhere here a post mentions using Base64 ( https://fmforums.com/topic/99956-base64-encodedecode-problems/?tab=comments#comment-454989 ) so I most likely misconstrued what he was trying to get at. About the custom XSLT stylesheet--is that something I can use to encode the card so it's good-to-go if it's sent by e-mail, or is that something the end user would have to have to convert the file from XML?
  14. Greets, all: I'm looking to incorporate vCard creation into an FMP solution I'm working on, but the scripts I've found on the Web harken back to FMP v13* and earlier (before Base64 encoding) and they're a bit unwieldy to work with. Does anybody have, or can point me to, a script or custom function that'll create Vcards that's more recent/elegant? Thanks, Rich *https://hbase.net/2014/10/22/exporting-vcards-from-filemaker-pro-13/. I'm probably being dense, but I don't see where the Virtual List Utility table is (as mentioned in the artile.)
  15. Ah, thanks. I deleted all but the Show Custom Dialog script step and added Exit Script [TestResult: False]. Yay!
  • Create New...

Important Information

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