I have a form protocol that sends comma-separated lists to the work protocol like this:

Parameters

             Registry_ID : 2, 1, 8, 18, 7, 10, 9, 20, 14, 22, 23, 11, 17, 15, 21, 3, 19, 12, 5, 6, 4, 13, 16

             Protocol_Number : M10-070

             Initial_Registration_Release : 12/22/2007, , , , , , , , , , , , , , , , , , , , , ,

             Writer : -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1

             Registration_Comment : Please note that we do not consider the volunteers in the study as patients and the study is a Phase 1 study, where there is no potential treatment benefit to the subjects. 3/8/2012, , , , , , , , , , , , , , , , , , , , , ,

In the work protocol I convert the lists to arrays using Expand and then create properties and unmerge to assign the values to the properties. So that this can be used by SQL INSERT.

The problem is with “Registration_Comment” field. It contains commas – so, converting like this:

Expand (',', @Registration_Comment);

messes comments up.

“Registration_Comment” field comes from a TEXT BOX in the form protocol. Text box has an option “Array Value Display” that determines the array value separator. Changing from “commas” to “new lines” does not do anything – the lists still come comma-separated. It does not have any other options.

Is there any way to replace comma to another separator before it comes to the work protocol? So that parsing would be not on commas? Or any other solution to the problem?

Thank you