Jump to content

Calculation Field- go from text values to #s


This topic is 6952 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hey. I am an amature and am working on an evlauation database for work. Any help would be appreciated:

I have a whole bunch of fields that have the same value list: "Completely Disagree", "Maybe", "Agree Somewhat", "Agree Fully". I need to be able to create reports with these fields where the fields can be evaluated as numbers, so that there would be able to be percentages of each different value, etc.

I assume I need to do a calculation field coverting the values to numbers. I can't figure out the Case function in calculations.

Can anyone provide help?

What I have guessed so far is:

Case (I can plan a research evaluation project from beginning to = "Completely Disagree", 1 [ I can plan a research evaluation project from beginning to = "Maybe", 2,

Will this work? How do I complete it?

THANKS!!

Link to comment
Share on other sites

Hi Jesse,

"I can plan a research evaluation project from beginning to" wins the prize for the longest field name ever used (I've been keeping track).

You can set up a case function like this:

Case(

I can plan a research evaluation project from beginning to="Completely Disagree",1,

I can plan a research evaluation project from beginning to="Maybe",2,

I can plan a research evaluation project from beginning to="Agree Somewhat",3,

I can plan a research evaluation project from beginning to="Agree Fully",4)

Link to comment
Share on other sites

Jesse, when you say you have 'a bunch of fields' - those fields are questions? And they aren't even called Question #1, #2 etc, but instead the questions themselves - as portrayed in the above calculation?

Hopefully you are very early-on in this design. Evaluation/quiz-type solutions usually go relational because you will have multiple questions, multiple answers and (Lordy be) multiple participants as well.

I think you will make this much harder on yourself than need be, as you constantly add new fields (questions), modify existing fields (questions) and then struggle to extract the data in meaningful groups (as you are discovering). crazy.gif

Lucky for you - you have come to the right place for support. And welcome to FM Forums by the way! grin.gif

LaRetta

Link to comment
Share on other sites

I need to be able to create reports with these fields where the fields can be evaluated as numbers, so that there would be able to be percentages of each different value, etc.

If you only need to report on a single field at a time, then it's not necessary to convert the text responses to numbers. A simple sub-summary report will work, using a couple summary fields and a getsummary calc.

However, if you need to results for multiple questions on one page, then you'll either need to redesign your survey to be relational, or add a file to hold the summary data for each question's choices.

Link to comment
Share on other sites

WOW. Thanks for the help.

Maybe you all can help even more, I am realizing I am way out of my league. This is a databse for evaluation data, and though I set up the data entry stuff really easily, now I am totally lost for setting up reports. Basically, my director needs simple reports, but with potentially complex data. He needs to be able to see the percentages for each response for every questions, based on found sets of records.

I will attach the file, and you can laugh at how much harder I made this than necessary. I think I made way more work than necessary to complete it, but now here is where it is at.

Can anyone offer a simple solution to the mess I have created based upon my reporting needs??

THANKS ooo.gif

POST.fp5.zip

Link to comment
Share on other sites

Jesse, I don't have time to give a suggestion about a report but I noticed something else you really need to consider:

You are using checkboxes for your selections. I assume you only want them to select one? It's best to use radio buttons instead of checkboxes because checkboxes allows multiple selections (unless you use field validation) and stop them. And field validation is not very friendly to Users ... best to only allow them to make one selection instead. smile.gif

Link to comment
Share on other sites

This topic is 6952 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.