Multiple Logins Required

I agree that it seems redundant, given the existing Favorites and Recents lists.  There are a few reasons we do this:

1. Hide most databases from end users, since they don't need to access them directly (they don't show up in Open Remote)
2. Sometimes things change -- filenames, host names, etc. -- and my users get confused
3. The launcher gives the flexibility to add files on multiple hosts
4. New files can just appear in the launcher

Keep in mind that most of my users are lawyers, so they really can't do anything terribly complicated.  ;-)

Using the small launcher means I never have to walk them through adding to Favorites (which until now I've had to do distressingly, depressingly often).  Giving them the launcher has eliminated 99% of the problems they have opening files. 

I still don't understand the benefit of having a FileMaker shortcut instead of a simple URI shortcut with a fmp:// scheme.

It would be so great if we could add a file to favorites during the installation and by script step.

Avoiding this issue for my users is the main reason I created a small "launcher" database for them.  They don't need to log in to the server at all as the launcher already knows the URIs for the servers and databases they need.  They have a desktop icon to open the launcher in FileMaker.  (The ONLY problem that has arisen since then is one user asking, "I don't understand about signing in to Google."  Well, you have to authenticate somewhere.  The launcher even tries to close the browser window after signing in successfully.)

Hi Linda,

The double login can be disabled on demand, but quite frankly, it's a very efficient way of 'obscuring' your databases.

You can easily add your database to your FileMaker Pro/FileMaker Go favorites to avoid having to go through the 'Hosts' dialog.

On Web Direct, you can go directly to your app by using the URL: https://<yourserver>.fmcloud.fm/fmi/webd/<databasename>