Beta v 17.4.59 Error - Reports -pref

For complex topics that regular users would not be interested in. For power users and database administrators.

Beta v 17.4.59 Error - Reports -pref

Postby drtech » Tue Apr 24, 2018 10:25 am

Beta v 17.4.59 - Program is crashing when I try to run Outstanding Ins Report. Looks like there is a pref Name issue? (Linux server)

Unhandled exception from ProgramEntry: OutstandingInsReportDateFilterTab is an invalid pref name.
System.Exception
at OpenDentBusiness.Prefs.GetOne(String prefName) in C:\SVN\beta\OpenDentBusiness\Data Interface\Prefs.cs:line 118
at OpenDentBusiness.Prefs.GetOne(PrefName prefName) in C:\SVN\beta\OpenDentBusiness\Data Interface\Prefs.cs:line 111
at OpenDental.FormRpOutstandingIns.FormRpOutIns_Load(Object sender, EventArgs e) in C:\SVN\beta\OpenDental\Forms Reports\FormRpOutstandingIns.cs:line 891
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO

Re: Beta v 17.4.59 Error - Reports -pref

Postby adearmondsattler » Tue Apr 24, 2018 10:53 am

Looks like you missed a convert script somehow.
What is the datatype for the GroupNum column on the Insplan table?
“If debugging is the process of removing bugs, then programming must be the process of putting them in.”

Allen DeArmond-Sattler
Open Dental Software
http://www.opendental.com
User avatar
adearmondsattler
 
Posts: 163
Joined: Fri Aug 23, 2013 11:29 am

Re: Beta v 17.4.59 Error - Reports -pref

Postby drtech » Tue Apr 24, 2018 11:52 am

SQLyog shows: InsPlan | Columns | GroupNum, varchar (25), Nullable
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO

Re: Beta v 17.4.59 Error - Reports -pref

Postby adearmondsattler » Tue Apr 24, 2018 12:05 pm

Thats strange. The code that inserts that is located in the same method and was committed before we released version 17.4.53.
If you self-compile and update it is possible that you missed some of a convert script.
When did you update past version 17.4.53?

If it reached the end of the method/you had the most updated convert script code, then this preference "ClaimPaymentNoShowZeroDate" should be the date you performed the update to 17.4.53, barring any manual changes.
“If debugging is the process of removing bugs, then programming must be the process of putting them in.”

Allen DeArmond-Sattler
Open Dental Software
http://www.opendental.com
User avatar
adearmondsattler
 
Posts: 163
Joined: Fri Aug 23, 2013 11:29 am

Re: Beta v 17.4.59 Error - Reports -pref

Postby drtech » Tue Apr 24, 2018 1:39 pm

yes, I self compile. 17.4.42 on 3/14/18 @ 11:35AM --> 17.4.52 on 04/11/18 @ 3:47PM, (but maybe it was really some of 17.4.53?) and then the next compile was 17.4.59 4/22/18 @ 2:55PM (as reported by the update window on OD "Help | Update | Show Previous Versions" menu and button)
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO

Re: Beta v 17.4.59 Error - Reports -pref

Postby jsalmon » Tue Apr 24, 2018 1:51 pm

If you're tired of getting this problem, a workaround would be to always utilize the SVN Update to Revision option instead of the normal Update option and then always choose a revision that has Version X.X.X.X as the commit log. That is an official release commit which would make it so that you aren't at a version prior to it being officially released to the public (which is what caused you to miss the convert script).
The best thing about a boolean is even if you are wrong, you are only off by a bit.

Jason Salmon
Open Dental Software
http://www.opendental.com
User avatar
jsalmon
 
Posts: 1464
Joined: Tue Nov 30, 2010 1:33 pm

Re: Beta v 17.4.59 Error - Reports -pref

Postby drtech » Tue Apr 24, 2018 1:52 pm

Pref.ClaimPaymentNoShowZeroDate = 04/04/2017
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO

Re: Beta v 17.4.59 Error - Reports -pref

Postby drtech » Tue Apr 24, 2018 1:54 pm

ok, yes, I would like to avoid it in the future, so I will see if I can figure out what you mean on SVN then to update to a certain stop point as this did happen to me last year once as well. How should I fix this issue?
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO

Re: Beta v 17.4.59 Error - Reports -pref

Postby jsalmon » Tue Apr 24, 2018 3:56 pm

The foolproof way would be to use a backup that you have prior to the version with which you are partially upgraded to.
The hard and dangerous way would be to look at each query that gets run in each of our version methods and determine if you need that query to be run or not and then manually run the ones that you deemed were not actually run.

Many of our queries within the convert script make the assumption that you have not been utilizing the version above them AT ALL so the hard and dangerous way mentioned above is still not a 100% guarantee solution for this issue. Reverting to a backup would be the only guarantee. It is ultimately your call on if you are okay with losing and then reentering data OR are you going to roll the dice and see if you can patch your database back up to health.
The best thing about a boolean is even if you are wrong, you are only off by a bit.

Jason Salmon
Open Dental Software
http://www.opendental.com
User avatar
jsalmon
 
Posts: 1464
Joined: Tue Nov 30, 2010 1:33 pm

Re: Beta v 17.4.59 Error - Reports -pref

Postby Ardavan » Thu Jun 07, 2018 8:53 am

You (both of you) probably already know this but since you mentioned a Linux server I thought I'd throw it out there that table names are case sensitive in Linux.
There are 10 types of people in this world, those who will laugh at this joke, and those who won't. ~Annonymous Bug Writer
User avatar
Ardavan
 
Posts: 72
Joined: Sat May 15, 2010 9:10 am

Re: Beta v 17.4.59 Error - Reports -pref

Postby drtech » Thu Jun 07, 2018 12:13 pm

I corrected it manually for this one, but yes, Linux is case sensitive and I usually leave my installation as case sensitive rather than turning it off to find errors. This was not a case sensitive issue however, it was compiling non "released" code point and so it skipped a step in the update process later on.
David Fuchs
Dentist - Springfield, MO
Smile Dental http://www.887-smile.com
User avatar
drtech
 
Posts: 1574
Joined: Wed Jun 20, 2007 8:44 am
Location: Springfield, MO


Return to Advanced Topics

Who is online

Users browsing this forum: No registered users and 3 guests

cron