Skip to main content

NEVER EVER leave the default Admin account enabled in FileMaker

I hesitate even to bring this up, because this is Dangerous Knowledge.

When you create a new FileMaker database, FileMaker gives you a default login account, with a default name and password. I wish it didn't and in my opinion, it shouldn't. But it does.

So here's what you need to know: Never, ever leave that default account enabled.

When would this matter?

If the database is stored on your computer and never shared with anybody, keeping the default account enabled means anybody who can get into your computer, can open the database — as developer. Now, this isn't really as big a deal as you might think, because they could do this even if you didn't use the FileMaker default login account. (Hint: Password crackers.) That's one more reason why you need to be careful about the security of your computer.

But God forbid the database is hosted on a server that is configured for remote access! In that case, physical access to the server is irrelevant. Any Internet troll who knows or can guess the server's address can get into your database — as developer. What do I mean by "server configured for remote access"? I mean a server machine that sits in your office but which has been configured so you can get to it from outside the LAN. And yes, I mean every single one of those commercial services out there that host FileMaker databases.

When you create a new database, the very first thing you should do is delete the default account and replace it with your own. And of course, immediately store that info in 1Password!


Popular posts from this blog

Virtual List Basics

The conceptThe basic trick behind virtual lists is the wonderful GetValue() function. GetValue() takes two parameters: A list of return-delimited values A number specifying which value in the list to get

For example say you have a field in a single record called “List of Values” and it contains the following:

When that record is selected, GetValue ( MYTABLE::List of Values ; 4 ) will return “Doorknob”.

The brilliant idea is to replace the list of values stored in a field with a list in a global variable.

The basic implementation, part oneCreate a table called VIRTUALLIST. In it, define these two fields: VALUE NUMBER: a number field Value_calc: calc field returning text value, = “GetValue ( $$VALUES; VALUENUMBER )”. Make sure that this value is an unstored calculation.

Go to the layout for the VIRTUALLIST table and create some records. Later you can create hundreds or thousands, but right now just ten will do. Use ReplaceFieldContents to po…

Getting out of fullscreen mode in FileMaker Pro

In version 2 of Acquittal, our criminal defense case management app, we're doing some nifty stuff with windows, and that means we're finding out that even in FileMaker Pro 15, we still don't have quite all the tools we'd like for managing windows.  One problem is how to trap for the possibility that the user has switched into fullscreen mode. The other problem is how to get out of it.

Is this window in fullscreen mode?
This one's not too hard. This calc formula seems to do the trick:

Get ( WindowHeight ) = Get ( ScreenHeight ) and
Get ( WindowWidth ) = Get ( ScreenWidth)

That will return true if the window is in fullscreen mode, false if it's not.

Why does this matter? Because there are certain things that you can't do with a window if it's in fullscreen mode. In Acquittal, for example, there are times when we want to generate a second "sidecar" window, then display the main and sidecar windows side-by-side. Can't do it if the main window …

More about why I like the new navigation part in FileMaker Pro 14

I myself didn't completely "get" the navigation layout part at first. In this post I want to clarify a few things about the benefits of this new feature.

The new navigation layout part in FileMaker Pro 14 and FileMaker Pro 14 Advanced differs in two significant ways from the header/footer parts we've had since forever (and which we still have in 14):

Navigation parts don't zoomNavigation parts don't scroll out of sight
Well, it's a little messier than that, in reality. Let me elaborate on the messiness of it first, since the messiness may have some impact on why navigation parts took me a day or two to "get".

First potential confusion: objects in navigation parts don't zoom, but they are not completely inflexible. If you grab the edge of the window and make the window wider (I'm not talking about zooming the content, I'm talking about actually enlarging the window) then any objects in a navigation part that are anchored to both sides …