Choose Database  

This window will come up sometimes when you first start the program. You can also access it from the Main Menu by selecting File | Choose Database

These are the settings that allow your workstation to locate the MySQL database. If you are installing EZ2000 Plus Dental on multiple computers, this window will come up the first time you run the program on each workstation. Once you enter the necessary information, you won't have to enter it every time.

For Advanced Users

One benefit of EZ2000 Plus Dental is that you are allowed to run as many databases on the same computer as you want. You can freely switch between them using the dropdown list of databases. For most users, this may be irrelevant since you only have one database. But keep in mind that you can make backups of your database within it's original folder. So, from this screen you could select from a variety of snapshots of your database as it was in the past. You can also switch between your regular database and a backup that you take home on your laptop for read-only purposes. If you run a dental billing company, each doctor client can retain a separate database and you can switch between them very fast. (each office must also have a separate EZ2000 Plus Dental license).

The data itself is stored as an xml file called FreeDentalConfig.xml in the application directory. If the file is missing or deleted, EZ2000 Plus Dental will recreate it the next time it is run. There is no point in trying to make any changes within the actual file. All options are available from this window. This is the only data in the entire program that is not stored in the database for the simple reason that you have not yet established a database connection, so you do not have access to the database.

Middle Tier

Instead of connecting directly to the database, you have the option to connect to a Middle Tier which handles all of the database interactions. The advantages include better security and speed for multiple offices. Using the middle tier makes it impossible for the user to connect directly to the database. The user will never have access to the MySQL username and password used to access the database. It also prevents injection attacks when writing queries.