Default values and Automatic append

[Stan Mathews]

Re: Default values and Automatic append

Ok.

mypatient.zip

[JetLi]

Re: Default values and Automatic append

Ok.

[ATTACH=CONFIG]30265[/ATTACH]

Thank you so much Stan. I'll try to learn from your solution, and have to figure out how to compute the patient bill with discounts,
maybe my table design is not normalize, but i have to identify the bills for every type of bill on a report

[Stan Mathews]

Re: Default values and Automatic append

With a table structure such as I suggested you could summarize by patient by date range by type and total the fee. You could crosstab with patient as the row and type as the column and total the fee, filtering the records to be crosstabed by date range.

All sorts of possibilities.

[CALocklin]

Re: Default values and Automatic append

CAL. Do you ever use the Audit Trail feature?

I haven't used it in years. Most of my stuff isn't that critical and I didn't like the idea of having a huge text file out there will all kinds of stuff that I didn't care about. I'm also assuming that there is no built-in limit to the size of the text file and it would be up to the developer to set up a routine to periodically remove old info. A couple of my apps have been running for over 10 years and that would be a lot or "auditing".

But your question has me thinking and I should probably add that to one of the apps I use for "personal" stuff (tracking addon owners, my business info, etc.) and become more familiar with it. There's a possibility it might help me resolve some issues in customer apps.

By the way, in case you missed my last edit, I finally realized that Stan was referring to a dummy table with one field in it - and I completely agree that one field in a dummy table is enough.

[Al Buchholz]

Re: Default values and Automatic append

I think an audit feature is key to data integrity. ( and tracking who did what..)

While it may be something to maintain, it's saved my bacon a number of times.

There have been a couple of scripts/functions posted on the board that each take a different approach to the issue than the built in Alpha audit feature.

[JetLi]

Re: Default values and Automatic append

Yap I'll try that Stan, Thank you

[JetLi]

Re: Default values and Automatic append

Ok.

[ATTACH=CONFIG]30265[/ATTACH]

Stan, Thanks for your help with the sample that you made, it is really of great help for beginners to see a working sample and learn from it rather than reading, although we really HAVE TO READ but it will help beginners learn by learning from the samples of alpha experts. I still have one question about your sample, is it recommended or is it possible to just put all the code behind the buttons into one button? so that end users will just click one button and the bill of all patients not yet discharged will be updated. or maybe the patients family member will inquire about how much the bill is.

[Stan Mathews]

Re: Default values and Automatic append

The one button in the second sample does that. The first four buttons that only worked on one date at a time can all be combined into one button. They were created separately so that one could push one button, examine the tables to see what happened, push the next button, etc.

All you need to do to combine them is to edit the onpush event of the second button, right click on and copy the action script element, close and then edit the first button (top), paste in the action. Repeat for the third and fourth buttons.

[JetLi]

Re: Default values and Automatic append

The one button in the second sample does that. The first four buttons that only worked on one date at a time can all be combined into one button. They were created separately so that one could push one button, examine the tables to see what happened, push the next button, etc.

All you need to do to combine them is to edit the onpush event of the second button, right click on and copy the action script element, close and then edit the first button (top), paste in the action. Repeat for the third and fourth buttons.

Thank you Stan, great help for me as a starter

[Ted Giles]

Re: Default values and Automatic append

As for the Audit Trail. It will indeed create a large .txt file, so an additional process - like zipping it - should limit the space requirements.
The reason I have used it is where there may be a risk element in the data being deleted.
Example:
Care home has an Incident logged - say medication mismanagement accusation.
Duty team log the incident but fail to pass on the Incident so it doesn't get investigated.
Patient gets seriously ill, relatives sue.
Duty team deny receiving complaint and delete the event.

It's more a case of "if I get asked what was deleted and who deleted it", how would I answer.
The fact that the audit trail exists - especially in an environment where it is possible to track the user - sharpens up work practice.
While I'm rambling on, finding out who creates most duplicate clients is another point. The unscrambling of data where both records hold pertinent data but are different Client ID's is a nightmare.

[JetLi]

Re: Default values and Automatic append

Stan,
What are these?
append.m_key = ""
append.t_key = ""
append.m_filter = ""
append.t_filter = ""
append.type = "All"
append.m_count = 5
append.m_field1 = "PDATE"
append.m_exp1 = "@TPATIENT->PDATE"
append.m_field2 = "P_ID"
append.m_exp2 = "@TPATIENT->P_ID"
append.m_field3 = "ROOM"
append.m_exp3 = "@TPATIENT->ROOM"
append.m_field4 = "PROFFEE"
append.m_exp4 = "@TPATIENT->PROFFEE"
append.m_field5 = "DISCHGD"
append.m_exp5 = ".F."
append.t_count = 0
Are these commands fixed? are they applicable in any table? Why is this included which is a constant append.m_count = 5
And what will i do so that values will be extracted from a table?example, the prof fee and Room rate, as i saw in your sample is fixed values or constant values,i want to get the fees from a separate table.

[Stan Mathews]

Re: Default values and Automatic append

See this.

[JetLi]

Re: Default values and Automatic append

Yap i saw that Stan but i can't figure out how to get the values of append.m_exp3 = "400" and append.m_exp4 = "150" from another
table so that whenever users will change the rates it will be dynamically fetched from another table.

append.m_key = ""
append.t_key = ""
append.m_filter = ""
append.t_filter = ".not. Dischgd .and. pdate = "+s_quote(last_date)
append.type = "All"
append.m_count = 4
append.m_field1 = "PDATE"
append.m_exp1 = s_quote(last_date+1)
append.m_field2 = "P_ID"
append.m_exp2 = "@PATIENT->P_ID"
append.m_field3 = "ROOM"
append.m_exp3 = "400"
append.m_field4 = "PROFFEE"
append.m_exp4 = "150"
append.t_count = 0

[Stan Mathews]

Re: Default values and Automatic append

What is the name of the "other table"? How would you decide which record in the other table to use if you did it manually? What is the name of the field that holds the value you want to get?

[JetLi]

Re: Default values and Automatic append

What is the name of the "other table"? How would you decide which record in the other table to use if you did it manually? What is the name of the field that holds the value you want to get?

Stan,
The name of the table would be:
rates.dbf
rateid type Amount
001 ProfFee 150
002 RoomRate 450
003 OtherFees 200

the other tables would be the one's from your sample.