Page 1 of 1

Encountered an improper argument

Posted: August 12th, 2014, 2:35 am
by rameshpal99
Dear Sir,

When I create section in dictionary, a dailog box comes automatically(encounter), I can't understand why it comes please help me....

Ramesh Pal

Re: Encountered an improper argument

Posted: August 12th, 2014, 10:49 am
by Gregory Martin
Selecting OK should be harmless. This is most likely due to a bug that was introduced in CSPro 5.0 but has since been fixed. The next release of CSPro should not display these annoying errors in the dictionary editor.

Re: Encountered an improper argument

Posted: November 7th, 2017, 12:12 pm
by ARSENE
Hi,

I also have the same problem.

I'm using CSPro 6.3. So normally, I should not see this message.

The worse is that it prevent me to continue developing my questionnaire.

How to fix it ?

Thank in advance for your responses

Re: Encountered an improper argument

Posted: November 7th, 2017, 2:15 pm
by Gregory Martin
This is a generic error message and the cause of it can be many things. I encourage you to upgrade to CSPro 7.0 to see if the problem persists with this new version. If so, please describe in more detail exact what you are doing when the error occurs.

Re: Encountered an improper argument

Posted: October 2nd, 2018, 4:47 am
by yodelibada
I just encountered the same error, using CSPro 7.1. It occurred as I clicked on an item to change its name.

Worse, it keeps appearing and taking over focus, preventing me from doing anything but manually shut down CSPro from the Task manager.

Re: Encountered an improper argument

Posted: October 2nd, 2018, 5:32 am
by josh
Can you give us more information about where you are getting this crash? Is this while editing forms or dictionary? Changing the name or label?

Re: Encountered an improper argument

Posted: March 12th, 2019, 1:10 am
by daniedusi
Im having the same problem, i have just updated to 7.2, what should i do?

Re: Encountered an improper argument

Posted: March 19th, 2019, 6:27 pm
by Gregory Martin
Unfortunately, this is a generic message and it is hard to know what the problem may be just by seeing that messsage. If you can explain what you were doing before you saw this message, we should be able to fix the issue.