#Filemaker pro for mac capacity how to#

If so, check: Have the unaffected user attempt to access the same part of the solution that the hung-up users are. Some users may be accessing a different file or a different table than the one causing the problem. However this is not necessarily always the case. If one user is being hung up by FileMaker Server, then probably all are. If it's the hourglass (Windows) or butterfly (Mac), then FileMaker Server is probably OK, and the slow event is on your local FileMaker Pro client. You can also get this when you're working remotely or on another otherwise slow connection and file data is being transferred to your machine. Something happening on FileMaker Server is hanging up your clients. What icon is on the locked-up user's screen? If it's the coffee cup (Windows) or Satan's Happy Spinning Rainbow Wheel (Mac), that means the server is busy. You need to know whether the culprit is on the server's end (FileMaker Server) or on the clients' end (FileMaker Pro). Back to performance problems: Slow Server, or Slow Client? But that can be discussed at another time. If your issue is corruption, take the file down from FileMaker Server now and work on it only in single-user mode, I don't care how critical your situation is. Anyway, we're talking about performance issues here, not corruption so the situation is different. I'm going to assume that your situation is critical enough that you can't do that. Obviously, it's best (and fastest) if you can take the system down to make such changes. This guarantees that Pro will maintain its connection to Server during the crucial moments otherwise you risk corruption. If you have to add fields, delete fields, change calculation fields in a large table, or anything like that, do it on the same machine as Server. Yes, you can open a file as a client on the same machine where it's being hosted. The one thing I will advise you to do - and I remind you, others will tell you not to do this, and on a non-emergency day I'd agree with them - is to make any changes to your schema using a copy of FileMaker Pro on the same machine as FileMaker Server. Most of the advice given here requires you to do development on a live server. Even if you weren't in crisis mode, many databases are simply too big to go through the process of taking everything down and exporting and importing data. The day the emergency hits is probably a critical time, and we often have to take critical steps. I promise not to condescendingly tell you to 'restore from a backup' or any crap like that. Wouldn't it be nice if we lived in Fantasyland and that was always practical? The reality is that we are often forced to do development, and especially emergency development like this, on a live system. Live DevelopmentĮveryone always advises you never to do development on a live system that's currently being hosted and used. You should read and know all of these, even if they're not relevant to your situation. Barcodes for FileMaker Pro - No Special Fonts, No PluginsĬode39 | Code128 | UPC-A | EAN-13 | POSTNET

#Filemaker pro for mac capacity how to#

How to fix it? We'll go through some of the more common causes. Business is being put on hold, perhaps disastrously. Your database has slowed to an unacceptable crawl. In this article, we're going to discuss this latter, more insidious, problem.

The performance bottleneck, on the other hand, is usually due to something obscure in your scripts, which makes it (a) ferociously hard to diagnose, and (b) your problem, since FileMaker's technical support can do little or nothing to help, beyond provide some general guidelines that you're probably already following. The total crash, while seemingly (and potentially) more disastrous, is usually easier to solve. There are two basic types of server emergency: The total crash, and the performance bottleneck. January 2010 Solving Performance Emergencies with FileMaker ServerĪnyone who uses FileMaker Server in a mission-critical capacity has either had to deal with an emergency, or they're going to. Solving Performance Emergencies with FileMaker Server