Jump to content

droid

Members
  • Posts

    10
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Maple Ridge, BC, Canada

FileMaker Experience

  • Skill Level
    Intermediate
  • Application
    18

Platform Environment

  • OS Platform
    Mac
  • OS Version
    10.15.4

Claris Partner

  • Certification
    Not Certified

droid's Achievements

Rookie

Rookie (2/14)

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

Recent Badges

0

Reputation

  1. Thanks, "comment". This database, with numerous tables, has never been cloned. The process of re-importing the data into each table, would be daunting. So I agree with you that there's no reason to explain the YYYY/MM/DD input coercion. Or is there...? "Current System Settings" is the File Options setting. You forced me (thank you) to think about my System Settings. Which were YYYY-MM-DD. Both problems are solved. THANK YOU AGAIN!
  2. Hello, I've been a Filemaker programmer for a long time, but on occasion I lose track of something that I should understand. A file has somehow gotten its date input formats switched around. My preference is to be able to enter DD/MM/YYYY, but I've done something to cause it to insist on YYYY/MM/DD. Related question, possibly? What is causing this dialog to appear, when opening just one particular database file? Not the same file as in the first query? Thank you!
  3. Wim, I've wasted your time. It was a bogus error message. The problem was that the pdf that was being referenced, had gone missing! Problem solved.
  4. Geez, fm19 is now out? I guess that’s why I managed to buy 18 cheap! Thanks Wim. That container field is visible and clickable on the layout. The script is launched, giving options to export or delete the contents. But choosing “export” Produces the error message. if I get a chance later in the day, I’ll post the script. But again, nothing has been changed from the versions that worked before.
  5. I've been saving various files - mostly pdfs - in FM container fields, for years. A script triggered by clicking in the field allowed the field to be exported for viewing. Recently I upgraded to FM18, and now when I click in the field, I'm told "container fields cannot be exported"! Is there a new way that I should be doing this? Thanks.
  6. BTW, about that flashing-by-too-fast dialog, that happens after I cancel the re-login: I have yet to be able to capture it by taking a screen video, but I have managed to discern that it starts with "Cannot reconnect". It happens when I am cancelling login to two FM files, one of which has opened the other. I have decided that is just telling me that file A cannot reconnect to file B, so I'm no longer concerned.
  7. Thanks Wim!
  8. Yeah, I had the same thought as I was submitting my question. What about the inactive interval, that determines when the re-login is necessary? Is it changeable?
  9. Sorry: Single user, Mac. If you can direct me to the appropriate FM Help resource page, I would be grateful. Arggh! I meant to ask: "That dialog that flashes by in about 0.1 seconds when the last re-login is CANCELLED, what does it say?"
  10. I recently purchased FM18, upgrading from 16. I find myself bemused by the "new" requirement to login again to a database, after a period of inactivity. Is there a way to adjust the inactive interval, make it shorter or longer? That dialog that flashes by in about 0.1 seconds when the last re-login is completed, what does it say? Thanks!
×
×
  • Create New...

Important Information

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