Jump to content

IdealData

Members
  • Posts

    2,691
  • Joined

  • Last visited

  • Days Won

    14

IdealData last won the day on November 18 2019

IdealData had the most liked content!

Profile Information

  • Slogan
    IdealData
  • Gender
    Not Telling
  • Location
    Leeds, UK.

FileMaker Experience

  • Skill Level
    Expert
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    High Sierra

Recent Profile Visitors

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

IdealData's Achievements

Grand Master

Grand Master (14/14)

  • Conversation Starter
  • Week One Done
  • One Month Later
  • One Year In
  • First Post

Recent Badges

28

Reputation

5

Community Answers

  1. In your original post you mentioned “a client needs this soon”. Is your client also running v14? If so, how do they propose to keep their system operational? v14 is now over 5 years old and is no longer supported.
  2. No, I am referring to CHROME on your phone - it's obvious then. You are running CHROME on your phone, aren't you?
  3. I'm no JS pro either. Check out qrserver.com It's an online solution but you could collect lots of qrcodes to use later.
  4. I downloaded and can confirm that FM Go 16 fails. Maybe this has something to do with it - it looks like a platform issue. https://community.claris.com/en/s/question/0D50H00006dsmn6/fmp-go-17-web-viewer-with-js-not-working
  5. If you're using WebD on Android then stick to Chrome (that's the only supported browser anyway). I'm not sure which browser you're running there but it don't look like Chrome. Make sure "Desktop Site" in NOT checked on the top-right menu. That would give the exact result you are describing. Incidentally, WebD works very well provided you allow it do so. I have an entire business management solution that runs all platforms and all devices. I also use 320px wide, but only 480px height to accommodate older phones., but that's really a design decision that's over 4 years ago. Newer releases of FM Server have raised the bar for both iOS and Android platforms and a 320px wide phone that meets the specs is unlikely to be even available now.
  6. Hi I am not an expert with PHP but see below some points that might get you a better performance.. You don't mention the specs on your hardware but I'd expect something pretty serious - SSD + 16GB + 8-Core?? This is something you can address easily. Is your solution in multiple files? How many tables? How complex? How many internal FM users? Adjustments here will obviously take longer. AFAIK the PHP engine is fed by XML calls. I'm not sure how the REST API is fed but it would make sense if it WAS NOT from XML as future editions of FMS are certainly heading towards the REST API and the PHP outlook is looking uncertain (the Linux version distinctly says there will be no PHP/XML options) and general advice is to go with the REST API. Is your PHP optimised? When FMS returns data to the PHP or REST API then it is based on the target layout and returns all the fields on the layout. This includes fields which are outside the normal viewing area too! If you pursue the SQL data method then the ESS performance hit will land on the internal FM users. Can't comment on MirrorSync but you sound like you understand it pretty well. Have you considered WedDirect? WebD offers the ability to implement multiple worker machines to spread high load situations - but your licensing costs could be dramatic! Sorry, no actual answer but do use this as a checklist.
  7. My understanding is that the ExecuteSQL statement will not rely upon the context of the layout, so any layout will do. FileMaker layouts are all about context, and you must be on a layout to do anything; but not everything needs context.
  8. As Fitch says, prove the data is missing first - it may just be missing the relationship key or other data that's obscuring it. In particular look at the data as a list or table view - and check the Get(RecordID). If there are gaps then that proves the records existed at one point. You don't need a button to delete records in WebD... 1. Are the menus available to the user? 2. Did you check ALL the relationships? Cascade deletes happen if there's any single instance of a table occurrence (with "delete related") even if you didn't delete the record from that context? 3. Cascading deletes can work BOTH ways. If you have the relationship setup to delete the parent when the child is deleted then you could easily achieve your situation. 4. Did the WebD session terminate or lose network? 5. Is the user using a compatible browser? Check application and version compatibility with your server. Your application should be checking and validating the web browser at start up. FileMaker does not prevent incompatible browsers. 6. Is there any scripting involved? That's your bag. Getting the wrong context is all too easy. 7. New user?? Mmm... I'm taking note of your "newbie" status so some of the above might be obvious if you're a more experienced developer.
  9. Thanks Laretta. Now i just need my download links that are now 72 hours overdue!
  10. Can you point me to this new script step in the online help guide please. https://help.claris.com/en/pro-help/#page/FMP_Help%2Findex.html
  11. Sounds brilliant - but I can't find it in the online help.
  12. All of the curl commands require a space before them so, & "--data-binary @$file\"" & Char(13)&Char(10) should be & " --data-binary @$file\"" & Char(13)&Char(10) I'm not convinced you need the CR/LF pairs. Also, have you tried running the curl command manually - from the command prompt?
  13. Is the Content-Type correct? If this is PDF should it be application/pdf?
  14. In your child file you need to capture the script parameter. Are you doing that? Set Variable [$sp = Get(ScriptParameter)]
×
×
  • Create New...

Important Information

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