Jump to content

fyanesv

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About fyanesv

  • Rank
    member
  • Birthday 07/26/1960

Profile Information

  • Title
    CEO
  • Industry
    Telecomunications
  • Gender
    Male
  • Location
    Venezuela
  • Interests
    Technology, Music, TV Science, TV Sports, Golf, Helping

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    15 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    El Capitan

FileMaker Partner

  • Certification
    Not Certified

Recent Profile Visitors

1,732 profile views
  1. Hi there, just having the same problem here, came across this issue: QuickFind wont work if "ifqf" option is selected on portal fields within a popover on a local machine (i tried different macs), but hosted on windows server 2016 FMS15, works just fine.
  2. HI, MattyM Just came across your request, if not solved, try this CSS on your body overflow-y:hidden; best regards, Fernando A.
  3. Hi all, Finally I came up with something, I updated the Sample file to show the Idea for Replicating popover's behavior on a portal. Thanks. Sample 2.zip
  4. Hi, I’m really Stuck , any suggestions would be most appreciated. Problem : I need to replicate a particular behavior of the PopOver that is inside a Portal. Behavior: When inserting or editing portal Rows via popOvers, the data updates in the portal before “committing”. Solution: Trying to replicate this behavior according to this rules: -. Using Transactions and Data modeling. .- Data not updated at the portal before committing (refreshing portal by trigger or exiting a field doesn't work). .- Data not updated at the portal
  5. Thanks very much Josh, and sorry I did not comment before, just came out of a nasty virus! and lost too much valuable time. I did email Todd asking for his thoughts and he posted the article. I guess there is not much I can do for now, I'll try understand the use of transactions and see if it helps. Once again many thanks to you and Wim, really appreciate both your time.
  6. I inserted a dialog and a Set Variable "Global" as first step at the Commit Script but It seems that it does not fires the onRecordCommit, this is what it does 1.- Immediately Commits the Record ( Viewed with simultaneous FMP Client Session) 2.- Fires "OnFirstWindowOpen". 3.- Goes to 1st Record. Don't know what else to do.
  7. Hello I've set up a FM14 database, hosted on FMS 13 Win, The database controlls commits to be possible only when certain field conditions are met and a submitting button is selected. Everything was working fine as expected via Webdirect until I notice that by refreshing the browser you get a not desired or Uncontrolled "commit". is there a way to avoid these?, Somewhere in the web I read that Refreshing the browser has the exact behavior that the "Exit Application Script" does on FMP client, which works fine under FMP client but I can't reproduce the same behavior under WD. I also read that
  8. Hi Bruce! I see what you are saying, and you are right!! maybe in cases where the found set is not relevant, its just another easy way!
  9. Hi All, About refreshing after exiting the portal, I use this combination that I came across by trail & error to refresh the layout and hide the objects: Commit Records/Requests [No Dialog] Show all Records Hope its useful,
  10. Wow!, Thanks eos, missed those two functions, never mind my script.
  11. Hi, For any one looking for a different solution I wrote this simple script called "Get Front Tab Panel Value", no plugins, use as standard for any number of tabs, just use Script Trigger with the help of Optional Script Parameter. The Global Variable "$$Front_TabPanel" holds the Active Tab. One time Script: Set Variable [ $Loop_Count; Value:2 ] Set Variable [ $N_Parameters; Value:GetValue(Get ( ScriptParameter );1) ] Loop If [ GetLayoutObjectAttribute ( GetValue( Get( ScriptParameter );$Loop_Count) ; "isFrontTabPanel" ) ] Set Variable [ $$Front_TabPanel; Value: GetValue( Get( Scri
×
×
  • Create New...

Important Information

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