Troubleshooting Error Code 802 and FileMaker Go Bug - Update

Error Code 802: Unable to Open File

While helping develop a FileMaker Go solution recently, we hit an unexpected snag (is there any other kind?) late in development cycle.  Our stand alone solution is designed to automatically connect to a FileMaker Server to get updated information on a routine basis every time it starts up. Since our clients are not always able to connect to the internet, we have code to allow them to safely bypass the check-in if that is the case.

Towards the end of the development cycle, we activated the code to make the call, and started testing.  And immediately ran into problems:  FileMaker Go version 15 connected right away.  FileMaker Go 16 connected with one user, but not another user.  Both were using the same beta version of the software, both had the same version of FileMaker Go:  v 16.0.4.   One of the first steps in troubleshooting is to add error capture code in order to see what is going wrong,  We did that, and were rewarded with error code 802:  Unable to open file.  Which is something we knew, of course.  But why could one user open it and not another?

The Search Begins

So I looked for some help on the internet and found that error code 802 had been puzzling people going back to 2004, and there were a variety of causes:

• Permission errors


• Database source not open on the server


• No reason, just happens occasionally


• Inaccurate database relationships


• FileMaker server bug


• DSN managers trying to setup a connection via ODBC


• Overloaded server

The list went on, and every solution identified did not apply to our situation.  The server file was present and available on the server to FileMaker Go users, and was accessible by using Open Remote directly from FileMaker Pro client, as well as FileMaker Go 15 (a requirement for this project).

For the record, our setup is pertty straight forward:  The FileMaker 16 server is housed on an AWS (Amazon Web Services) server, and is the limited developer version allowing one concurrent hookup.  Only one user was connecting (and immediately disconnecting after running a short script) at a time, so too many concurrent connections was not the problem.

After thinking about FileMaker 16 differences from earlier platforms, a thought occurred:  This might be a security problem with FileMaker 16's new, rigid SSL requirements.  I checked, and our temporary FileMaker SSL certificate, issued by the FileMaker Server for development purposes, had expired.  Every time a new user tried to connect to the server with FileMaker Go 16, the server threw a popup warning that the connection to the database on the server was not secure.  During a normal connection via FileMaker client, this is not a problem, as the user can click the button to proceed.  When logging on via a script, however, this option was not available, and the file would not open - Error 802.

Problem solved

We were able to connect every user by simply adding a Host entry with the IP address to the iPad – when a user adds the host, the security warning shows up during the process and the user can permanently add the server to the approved list.  Short term, that works out.  I later added an SSL certificate to the server, solving the problem in the long term.  And a valid SSL Certificate is something necessary for almost all FileMaker Server installs with containing sensitive data (the exclusions include local servers inside a secure firewall).

So add one more option to Error Code 802:  Unable to open file via script due to SSL Certificate requirements with FileMaker 16.

---

FileMaker Go Bug - UPDATE

I reported what I suspected was a FileMaker Go bug on Monday here.  It turns out to be the real deal:

Thank you for your posts and movie file.  I am able to reproduce the issue with FileMaker Go 16.0.4 under iOS 11.2.6 using an iPad Pro.  I have sent all information, including a sample file, to our Development and Testing departments for review.  When I receive any feedback, I will let you know.

TSGal

FileMaker, Inc.

Hopefully, it will be patched soon.

FileMaker Go Bug?

FileMaker Go Bug?

I am working with another developer on a big rollout for a primarily iPad based solution. We are using sliding panels as a major interface feature.  In the development process, we discovered a FileMaker Pro Bug.

The app is feature packed and has multiple sliding panels on each major interface page.  On some layouts, up to seven sliding panels are stacked on top of each other. While this results in a more complex development environment, the resulting user experience (UX) is impressive and has a reduced learning curve.

And it all works well on Mac’s and PC’s.

Using FileMaker Client on a Mac or a PC is not a problem.  When we programmatically activate a sliding panel, that panel assumes “Active Focus”, meaning the panels essentially drop behind the Active Focus panel despite their relative position in the stack.

For example, activating the 7th (lowest) panel in the stack using the “Go to Object” command essentially brings that sliding panel to the top of the stack.

Once on top, all functionality you would expect does work:  filed access, scrolling, popovers, button access, etc.  But...

Portal Scrolling does not work FileMaker Go

On FileMaker Go, however, there is a major problem.  Calling the 7th panel and giving it Active Focus on FileMaker Go works for all functions save one: scrolling a portal.  Watch this short video to see the bug in action:

[video width="1468" height="752" mp4="http://www.filemakerprogurus.com/wp-content/uploads/2018/03/FileMaker-Go-Bug.mp4"][/video]

Steps we have taken to try to squash the bug:

We reviewed all of the Window script steps:  Since the panels are placed on a Window, those commands were not effective.

We also tried various Navigation commands, and I suspect we could build a script to go to a record in a portal and force a scroll, but that is clunky and not intuitive to the user.

The only thing we have found that works is to hide the slider using “Hide Object When”.  The problem there is the logic it takes to properly hide up to 7 different sliders using conditional logic. It can be done, but only after all design considerations have been locked down.  Adding any new features sends us back to the logic maze with plenty of testing to ensure all works OK.

In the hope that there is a work around we have not yet discovered, I am posting this on various forums and with FileMaker, and also posting here on my blog.

Please leave a comment if you have an idea.  Your feedback is appreciated.

FileMaker and Shippo, and the 2–Minute Rule

Shipping Labels Using FileMaker and Shippo

Brandon Ray, of DB Services, posts a great how to do it article on integrating FileMaker with Shippo, an inexpensive online service that allows you to use just about any major shipping service.  Shippo provides an easy way to get shipping costs and allows you to print the label, too.  And all for a cost of only a nickel over the cost of shipping.

There is one small catch.

You'll probably have to double enter the customer's shipping information:  Once into your order system, and once into Shippo.  Errors creep in when double order entry is needed. But, no worries!

Ray's solution gives step by step instructions for connecting your FileMaker solution to Shippo....or you could just download the free FileMaker Example file at the link below and integrate that with your solution.

Source: FileMaker Shipping Labels with Shippo

 

The 2–Minute Rule

James Clear is back with research on how to stop procrastinating with what he calls the 2–Minute Rule.  It boils down to one simple observation:  Most things you put off are easily done, you just don't get around to doing them for some reason.  The 2-Minute Rule addresses that problem by defining an issue thus:  If it takes less than two minutes to do, then do it now.

The 2–Minute Rule works for big goals as well as small goals because of the inertia of life. Once you start doing something, it’s easier to continue doing it. I love the 2–Minute Rule because it embraces the idea that all sorts of good things happen once you get started.

• Want to become a better writer? Just write one sentence (2–Minute Rule), and you’ll often find yourself writing for an hour.


• Want to eat healthier? Just eat one piece of fruit (2–Minute Rule), and you’ll often find yourself inspired to make a healthy salad as well.


• Want to make reading a habit? Just read the first page of a new book (2–Minute Rule), and before you know it, the first three chapters have flown by.

I tired this, and it's easy to apply.  You only have to invoke the 2-minute rule.

But I have bigger to-do's than 2 minutes!

When you have something that takes longer to do than 2 minutes, something you've been putting off, just give it two minutes.  That often leads to working longer on it and getting it done sooner.  Read up on the science backing this concept at the link below.

Source: How to Stop Procrastinating by Using the "2-Minute Rule"

---

Getting information off the Internet is like taking a drink from a fire hydrant.

Mitchell Kapor