This forum is for programmers who have questions about the source code.
-
wjstarck
- Posts: 945
- Joined: Tue Jul 31, 2007 7:18 am
- Location: Keller, TX
-
Contact:
Post
by wjstarck » Wed Dec 23, 2020 4:08 pm
I have an issue starting in OD 20.4 where there is a copy of Open Dental running in the background even after the user quits OD on the desktop.
The next time Open Dental is started, it apparently assumes the freshly started instance is a second instance, so my plugin won't run. I have to force-quit this background process and then restart OD for everything to work again.

Last edited by
wjstarck on Fri Dec 25, 2020 3:04 pm, edited 2 times in total.
Cheers,
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
-
wjstarck
- Posts: 945
- Joined: Tue Jul 31, 2007 7:18 am
- Location: Keller, TX
-
Contact:
Post
by wjstarck » Wed Dec 23, 2020 7:13 pm
OD version is 20.4.32...
Cheers,
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
-
jordansparks
- Site Admin
- Posts: 5770
- Joined: Sun Jun 17, 2007 3:59 pm
- Location: Salem, Oregon
-
Contact:
Post
by jordansparks » Sat Dec 26, 2020 5:50 pm
Researching.
-
wjstarck
- Posts: 945
- Joined: Tue Jul 31, 2007 7:18 am
- Location: Keller, TX
-
Contact:
Post
by wjstarck » Wed Dec 30, 2020 12:58 pm
Would a production db that had been updated in the debugger cause this to happen?
I didn't see the behavior on the live db on my laptop yesterday but still see it happen repeatedly on my development machine. Odd. The only other difference is my live db machine is running MySQl 5.6 and the development machine 5.5 but I can't see how that would cause this behavior.
Cheers,
Bill Starck, DDS
Big Idea Software, LLC
Developer, EASy(Electronic Anesthesia System) for Open Dental
817-807-1709
TX, USA
-
jordansparks
- Site Admin
- Posts: 5770
- Joined: Sun Jun 17, 2007 3:59 pm
- Location: Salem, Oregon
-
Contact:
Post
by jordansparks » Thu Dec 31, 2020 10:50 am
When in VS, there are two ways to terminate a program. You can click stop in VS, or you can close OD itself. Clicking stop in VS should work 100% of the time, so I'm guessing your original screenshot was closing OD itself.
-
dcrider
- Posts: 67
- Joined: Sun Sep 29, 2019 11:03 am
-
Contact:
Post
by dcrider » Wed Jan 20, 2021 9:54 am
I can confirm that clicking Stop in Visual Studio does NOT kill the process
-
dcrider
- Posts: 67
- Joined: Sun Sep 29, 2019 11:03 am
-
Contact:
Post
by dcrider » Sun Feb 07, 2021 8:51 pm
This is happening on instances of OD that have been upgraded to 20.4.45
This prevents us from updating DLLs unless we remote into each computer (we have 26 offices in 4 States) and kill the process manually. This needs to be fixed.