[color:"blue"] Hi! Does anyone know if there is a way to customize the FileMaker error message that appears when a database is needed and it is not open? Any type of customized message would be useful, either an htm created by myself or modifying the FM response directly. Thanks!

Hi, Jonathan! I have not gotten around to it yet myself, but I think you can use IF to show custom messages for different error types on your -error page... My guess is that the -db not open error is a common one so should be easy. I'm away from my desk right now so cannot give you specifics, but if you cannot find anything after some hunting, I'll try to follow-up.

--ST

Thanks for your reply ST. I use that method on some web pages, but the problem is that the "db not open error" is not in the numerical list error, at least on FM4 which is the version I use. Does your version have it? Thanks for your help!

Hi, J! Huh. I couldn't find it in the list but I just ran a test using [FMP-CurrentError]. If I try to find field data that's not there, my -error page displays 401 for not found. When I close the DB, I get the DB NOT OPEN message and my error page does not load. I guess it's not a standard error after all.

Sorry. That's a bummer.

--ST

In order to serve FM over the web, the appropriate db files must be open.

With that in mind I fail to understand the logic of why a db file which is pertinent to the solution would be closed.

The answer seems quite simple really; obviate the need for a message, open all db files necessary to serving the solution and keep them open.

ST: Thanks for your help, I guess FM does not have this feature.

Unable: It could be closed because to update the database, which can take from 10 up to 30 minutes, the database must be closed. It is a short period of time but I would like for my clientes to see a nice error page telling them why the server is down and not the standard FM error message.

It'd be kinda weird, but I suppose you could write some kind of script (AppleScript, shell script, batch?) that changes the name of your index.html page and substitutes another message page as index.html while your db updates and then changes them back when you're ready to publish again.

--ST

Or it could be that one should not work directly in the db file which is being used to serve the www. Perhaps working in a current copy of the db file and then exporting the changes - or whatever.

Otherwise, use Steve's suggestion and close your site to clients, with the exception of a notice of maintenance - or whatever. Hell, you can substitute your index.htm manually for that matter. Go Fetch. No fancy scripting necessary.

Or maybe update (yeah, its expensive - but you could spend $30k+ plus on something more elaborate) to a more current FMPro, including Server and Unlimited. One can only get so far on the cheap.

Perhaps if it the site is not profitable in 4.0 so that upgrading FMPro is out of the question, the project should not be pursued. But that gets into economic theory and away from development. And economic theory is something for bosses. And they aren't too bright. When you get right down to the nitty gritty they're just cheap.

Cheep, cheep, cheep say the little chicks.

I just read this in the FM 5.5 administrator user guide:

The Web Companion recognizes these error pages in the Error

folder:

DatabaseNotOpen.htm

So FM4 cannot do it but 5.5 does...

So just upgrade all the way. To 6.x that is, and get Server and Unlimited and any other licenses you need. Tell them I sent you. Ha ha ha.