• Content count

  • Joined

  • Last visited

  • Days Won


webko last won the day on March 3

webko had the most liked content!

Community Reputation

52 Excellent

1 Follower

About webko

  • Rank

Profile Information

  • Gender
  • Location
    Sydney, Australia

FIleMaker Profile

  • FM Application
    13 Advanced
  • Platform
    Cross Platform
  • Skill Level
  • Membership
    FileMaker Business Alliance
  • Title
    Database Developer

Recent Profile Visitors

7,615 profile views
  1. Or make ItemRef lookup the value from the subtable as an auto enter option, or simply show the now related firld from the subtable - Category::ItemRef
  2. 20 The relationship sets the initial number of records being dealt with
  3. Here's good, probably the best - but what's your actual issue? The items not showing in the portal?
  4. I think the Hide When... functions only became available in FM Pro 13 After that you get into different layouts for for showing/hiding (blecch!)
  5. A text block has a position on the screen - let's say your original2nd text block with the suffix was left 300px, top 10px, right 400px and bottom 25px. Any text within it will start at 300px from the left. The other left text block may have started at 10px and have about 240px of text. The second block will still start at 300px, leaving a large gap. It's more obvious over multiple records where the end of the first text block will change, but the second will always start at the same point...
  6. LOL Lee... I just pointed out that if both merge fields are in same text black, this works. The problem was that the second text black had a fixed left point, leading to the extra space (and in other longer names, would cause on overlap...)
  7. What are these degrees people speak of?
  8. Why not create the merge from the related child records?
  9. Actually it does - Windows 10 is not a supported OS It may work, it may not but FileMaker will not guarantee that it will.
  10. If you log in to the the database without credentials, then you are not as far as the database is concerned.... And it affects that field, and the record - as that field is set to validate, if it fails then no change will be made to the record.
  11. The field Assessors Comments has a validate by calculation on it - Get(UserName) = "fairburna" or Get(UserName) = "fusseyn" or Get(UserName) = "clare" If you're not one of them, you get the message above.
  12. System Preferences > Language & Region > Advanced
  13. Use Not IsEmpty And make TOP_LocalCompany a text field with an auto-enter calc the same as the calc definition - I'm assuming the actual value doesn't really change very often
  14. I wil note that this is not done purely with the API - it's an FMStudio v2 generated page which uses some custom functions not used in the API. And that FMStudio went unsupported a few years back. It's also not a query page - it creates a new record, and reads data back from that record. That said, if the WebForm layout does have the value lists available when a brand new record is created (used for drop downs and buttons), this looks like it should work