Open Dental

Hey Jason, Thanks a ton for posting that, and don't misunderstand, I stake no claim on suggesting it will be an easy transition to 5.7 :oops: I'm not sure what we'll run into, but I'm happy to help in the process and give the clients a better product in the end. Our first venture is to simply just u...

There are actually a ton of benefits with 5.7, not the least of which is about a 33% increase in speed and efficiency. They also added more replication error controls and checks to keep replication working properly in power or disconnect events. None of these features exist in 5.6. I get that we'll ...

Can you please update the code to check the "default_storage_engine" variable instead of the "storage_engine" variable as it has been deprecated. We are trying to setup OD Central Management using MySQL 5.7 but can't update the db because of this check. We would also like to look at the all the repl...

In order to make some reporting tools we're using faster, we've implement various views in our database. Whenever we upgrade or run database maintenance from OpenDental it thinks the views are tables and are corrupt or don't belong so it stops upgrades from happening and won't fix regular database i...

Like the ability to add our own splash screen. 2 Questions about it:
1. Can you tell us the ideal size of the splash screen and if there any required text we should be displaying in it?
2. How do you get the Splash.jpg to automatically install on every computer?

Thanks for your help.

We have had providers who needed different Carrier identifiers in the Supplemental Provider Identifiers section of the Provider screen. I'm wondering why this was setup as an ENUM to only 4 carrier types. Wouldn't it make more sense to have this point to the carrier table so that we can attach IDs t...

We have been seeing ClaimPayments getting deleted from our system and haven't understood why. Our process is to get an Insurance Payment posted as soon as we receive it and mark it as Partial so that another person or team can apply the payment to specific procedures. I finally dug into the code and...

Just encountered a bug in the appointment move feature of the latest release 12.4. This feature was added when moving an appointment (not sure why, would like to know): LINE 3272 in ContrAppt.ContrApptSheet2_MouseUp: for(int i=0;i<procsForSingleApt.Count;i++) { procCodes.Add(ProcedureCodes.GetProcCo...

Any reason to not make this work with 5.5 now? I keep getting an error that is not a compatible version of mysql. 5.5 just went GA so it should be safe to allow shouldn't it?