Hello. I'm getting near the end of creating a database solution for a dental practice. It currently has 17 files. A few of the files have a large number of fields(650), scripts(150-200), Relationships(70) and Layouts(44). The program seems to run very well. One of the larger files will probably only hold 3000-5000 records at maximum operation. I'm a little concerned about the complexity of a few of the files. They seem to do well. Should I be concerned about the above numbers? I expect to be networking about 15 stations for the dental practice. Comments or suggestions on how to avoid future problems or maintenance concerns would be appreciated. Thanks.

FileMaker can handle all that quite easily - I would say the application is not your concern. What you've got to make sure of is that you completely document the solution, especially the scripts. There is nothing worse than discovering a bug/mistake once a solution is up and running, then having to trace through scripts to find what ought to be a simple fix.

One thing to be careful of is to make sure that whatever machine is hosting the databases is not used for anything else, whether you are web-sharing or using FileMaker Server.

-Stanley

Piece of cake for FM.

The only dramatic slowdown is calculation running through 100k or more records. That can and should be avoided by storing results of transactions and not recalculate always when layout with such calculation field is entered.

I agree with both Stanley and Anatoli - This is one of the reasons Filemaker Kicks butt as a development tool. And combined with Filemaker Server is should scale easily to many 1000s of records and many users.

Thanks everyone for the comments. It will interesting to see this project begin to breathe life with real use.