Search results for query: *

I found one at 325, counting characters and spaces. I don't think we'd go beyond 400.

Yes LB is correct, the final string could very well be more than 250. In fact in testing it will work fine till it comes to a record that exceeds the 250.

An individual memo field is never longer than 254 characters. The number of actual characters in the field can vary from 25 to 150. The accumulated for the larger case could easily exceed the 254. We are upgrading next year - guess I may have to wait. Darn - I was sooo excited! Thank you for...

Well almost there. When I query on only one case it works great! If I query on more than one case the formula editor box for the accum pops up and says "A string can be at most 254 characters long." I even created it as a subreport (thinking this is only pulling for each case reord) but I still...

You have attained god/goddess status in my book!!!! It works!!! I have struggled with this for years!!! Someone wrote me a view to try and do this and it slows the reports down so they are almost unusable!!! That's why I kept looking for another way to do this. You have no idea how valuable...

Sorry, version 8.5. These memo fields coincide with procedure codes. Its a free text description of a hard coded procedure - for example there are two coded procedures on a case one for a hernia and one for a removal of a lesion. The text field for the hernia would say "Repair right inguinal...

The database I use has some fields that are text_value/memo fields. They do not come up in the formula editor. Is there any other way to use these fields in crystal?

3 Groups 1. Site (main hospital or surgery center) 2. Surgery Date 3. Case Code - the unique identifier of a patients surgery visit. Variables to get the first and last pain scores and temps: reset is in the case group header, the "get" formula is in the details and the "show" formula and all...

Now the formula displays 0.00 for all records. There is a pain score in each case footer record and there are no suppressions - so I don't know where the "no records" comes in. I've tried moving the reset formula with the same results. Not sure what else to try.

When I put the running average formula in the cass_code footer I get a message saying "Division by zero". Zero is an actual pain score so there is no way to get rid of them.

No Problem. Believe me I asked plenty questions myself to understand what they wanted... They want an average across patients not per patient (Each patient will only have one 1st temp, one 1st pain score etc.). The records will be sorted by date so they will see a trend over time. Currently they...

This is for quality initiatives for our anesthesia department - they want to see improvement over time. Patients should enter the recovery room with lower pain scores and higher temperatures. If certain medications are started too soon in the procedure patients enter recovery room with high pain...

Here are the formulas: Re-sets: shared numbervar first_score:=0; shared numbervar last_score:=0; shared numbervar first_temp:=0; shared numbervar last_temp:=0; Get Variables: whileprintingrecords; shared numbervar first_score; if {DOC_PAIN.PAS_SERIAL} = NthSmallest...

I have several variables to get the first and last records of some fields. 1st pain score (numbervar first_score), 1st temperature (numbervar first_temp)etc...my reset formula for the variables is on change of patient header. I am told to calculate a running average for each record....like this...

There are no suppressions (that's what I loved about getting the data this way)and the selection is what I posted. I think I am going to rebuild the report from scratch and see what happens to the record selection along the way.

No because we use military time. So these are all am cases. I know it didn't make any sense to me - but I don't know much! If I comment out the % lines it shows up!

{CASEMAS.SH_SCHSTAT} = "S" and {CASEMAS.SH_START} <= "10:00" and {CASEMAS.SH_DATE} = {?Date Range} and {SYS_TREE_2.TREE_NODEID} = 1130 and {@DOW} in ["Friday", "Thursday", "Wednesday", "Tuesday", "Monday"] and {SYS_TIME.TIME_CON_STIME} <> "" and {CASEMAS.SH_ROOM} in ["SSC 4","SSC 3","SSC 2","SSC...

Here is the data with the 2 sql expressions commented out. The select criteria is looking for cases on 11/15 with a scheduled start time of 10:00 or less. You can see the Dalton case now shows up for ASC. Site Date Room Sched Surgeon ACH 11/15/2010 OR 01 08:00 BENDER, ELIZABETH ACH 11/15/2010...

Here are the 2 statements and the data sorted by site,room then date.I only ran for 11/15. I am missing the 9:30 Dr Dalton case in ASC Room SSC 1. %mintime ( select min("sh_start") from CASEMAS A where A."sh_date" = CASEMAS."sh_date" and A."sh_doclnm" = CASEMAS."sh_doclnm" and A."sh_site" =...

Ok, now one more thing..... It is completely excluding one doc. He only has one case at the ASC. All of the data in the record looks correct. If I comment out the mintime it shows up for ASC but the same report for the ACH shows all the duplicate docs. Here is the ACH data without the %mintime...