Procedure.UnitQty

This forum is for programmers who have questions about the source code.
Post Reply
User avatar
jordansparks
Site Admin
Posts: 5744
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Procedure.UnitQty

Post by jordansparks » Thu Sep 20, 2007 10:36 am

I think this field should be an int. Hopefully, you're not using it yet, and we can make that change simply. Without it being an int, all queries to determine production become quite a bit more complex. The one result of this is that we will have to set it to one for all new procs, but that won't be too hard.
Jordan Sparks, DMD
http://www.opendental.com

fdscadmin
Posts: 59
Joined: Thu Aug 09, 2007 2:33 pm

Post by fdscadmin » Mon Sep 24, 2007 1:37 pm

Yes. That would make sense for it to be an int. The same for BaseUnits. I am working on that section now, so I will make the changes.

User avatar
jordansparks
Site Admin
Posts: 5744
Joined: Sun Jun 17, 2007 3:59 pm
Location: Salem, Oregon
Contact:

Post by jordansparks » Mon Sep 24, 2007 2:05 pm

Lookout. I'm working on FormInsPlan as we speak. And also on the various related InsPlan files.
Jordan Sparks, DMD
http://www.opendental.com

fdscadmin
Posts: 59
Joined: Thu Aug 09, 2007 2:33 pm

Open Files.

Post by fdscadmin » Mon Sep 24, 2007 2:11 pm

I'm mostly working on adding base unit support to the procedure table and procedure log. I might need to update the "total" fee and estimate calculations to include base units if they are assigned.

Post Reply