Can I create a survey questionnaire using labview

[GerdW]

Hi frankenberry,

---

@frankenberry wrote:

Hey?! There are no learning resources at the top?

---

Look more carefully:

[frankenberry]

That's not at the top. That's under a different tab. That would have been helpful to know. These posts are under the 'Community' tab. It wouldn't matter how carefully I looked.

You know what would be really helpful? A section for people just starting out in NI and Labview. This should be available through their profile and right after they create and verify their login.

[GerdW]

Hi frankenberry,

---

@frankenberry wrote:

That's not at the top. That's under a different tab. That would have been helpful to know. These posts are under the 'Community' tab. It wouldn't matter how carefully I looked.

These "LabVIEW Training resources" are at the top of the LabVIEW board. (Exactly where they belong to.)

---

@frankenberry wrote:

You know what would be really helpful? A section for people just starting out in NI and Labview. This should be available through their profile and right after they create and verify their login.

---

There also is a forum board for "Feedback on NI community". Post your suggestion over there!

[frankenberry]

Not necessary. I don't find this thread very helpful.

[cbutcher]

Hi frankenberry,

I'd echo what others have already said about reposting to very old threads - there could have been a great many changes to LabVIEW in the last 12(/16? - I didn't check) years since this thread started.

However, in response to what appears to be your question, it should be possible.

Certainly, LabVIEW can do the following:

• Read CSV files
• Change the text in or next to buttons to use for answer clicks - this will be easier if the number is fixed, but is possible provided it is bounded
• Store answers based on some "username" provided at the beginning, or similar

Is that basically what you're wanting to do?

You should start with splitting your learning into those topics, assuming that you have some reason to avoid going through the more general training available at the top of the board (and if you didn't see it when you first came here, then perhaps giving feedback on the community page would indeed be helpful).

There are numerous articles (KnowledgeBase, White Papers, forum posts etc) about each of these topics.

The term "property node" will probably help you changing a buttons "boolean text".

File I/O should be easy enough to find, you can look specifically for spreadsheet parsing functions.

If you're using LabVIEW 2019, you could use the new Map type to store "results" with a username as key, but for older versions you could consider just an array with clusters of name, result (which might also be a cluster).

Read about clusters and typedefs before you start!

[altenbach]

---

@frankenberry wrote:

You know what would be really helpful? A section for people just starting out in NI and Labview. This should be available through their profile and right after they create and verify their login.

---

Not all new community members are interested in LabVIEW. There are many other reasons to use NI products. LabVIEW itself has a rich collection of help topics, design templates and example code.

---

@frankenberry wrote:

Which learning resources would be the most helpful for creating questionnaires (not surveys)?

---

Start with the basics. A questionnaire is basically a state machine. First you read the questions and answers from the file, then you present each question, wait for the answer, next, etc. until you run out of questions. Maybe log the responses to a file. You need to learn about dataflow, structures, decisions, etc. all very basic stuff. the only datatypes you need are strings, enums, and integers. How much programming experience (in any language) do you have?

[frankenberry]

Is there any example code for what I want to do (i.e., questionnaires)? My search of the entire site only turned up this very old thread. The site is not easy to navigate. It seems you need to be familiar with NI in order to get where you want to go and find what you need. The problem is that the collection is 'rich'. Where are the 'basics'? 

I'm doing several questionnaires and it seems counter-productive to have several 'answer' files when the 'answers' can be the same across questionnaires. For example, one questionnaire uses 'yes','no', 'sometimes', whereas another uses 'yes','no', 'sometimes', 'refused', 'does not know'. Would it not be more useful to have only one answer file that includes all the answers a participant/client would input? 

I also need to evaluate each questionnaire.

I have some experience but not a whole lot. I've programmed in Matlab (my stimuli are programmed in Matlab but will be presented through Labview and recorded in Biosemi), php (helped a programmer create an online system for an organization in Toronto and took an online course), html (for a charitable organization while completing my Masters), some Labview but never took any training.

Thank you for taking the time to answer my questions. If you can direct me to the 'basics', I can get started.

[RavensFan]

"I'm doing several questionnaires and it seems counter-productive to have several 'answer' files when the 'answers' can be the same across questionnaires. For example, one questionnaire uses 'yes','no', 'sometimes', whereas another uses 'yes','no', 'sometimes', 'refused', 'does not know'. Would it not be more useful to have only one answer file that includes all the answers a participant/client would input?

I also need to evaluate each questionnaire."

I don't understand your confusion about multiple question and answer files.

You have a question file.  (Are all your questions going to be multiple choice or do you need free-form type in the box?  Do you need the ability for multiple responses, e.g. "Check all that apply"?)

Question file would be a text file:

Question 1:  Age,  0-15,16-25,26-35,35+

Question 2:   Gender, Male, Female

Question 3:  Do you use LabVIEW: Yes, No

......

Read each row to get the question and the possible answers:

The Answer file would be:

Response 1:   26-35, Male, Yes

Response 2: 35+,Female, Yes

Response 3:  16-25, Male No

.......

Each time someone takes and completes your survey a new row is added to the answer file.

For each new survey, you'd have a new question file and a new answer file.

[frankenberry]

The question file would have questions, wouldn't it? Why is the example you gave including possible answer choices in the question file? Shouldn't it just contain the questions? And the answer file would contain possible responses. And the output file contains the response given by the participant?

[mcduff]

---

@frankenberry wrote:

The question file would have questions, wouldn't it? Why is the example you gave including possible answer choices in the question file? Shouldn't it just contain the questions? And the answer file would contain possible responses. And the output file contains the response given by the participant?

---

Just guessing here. Wouldn't it be easier to have one question/answer file to save you from the potential of bugs. Assume you insert a new question into the question file, they you need to also insert a new answer into the answer file and the same location(row, etc). For me it appears easier to upkeep one common answer/question file. Only 1 file to keep track of, instead of two.

mcduff