Online Survey with a programming language

Did I tell you about the programming language of our online survey solution ? I dont think so, let me tell you just a little about this survey programming language.

Our solution integrates a programming lanage which allows you to program your questionnaire, a logical language that allows you to chain questions.

For example if the first question of your questionnaire is : Are you a man or a woman ?

Then you can ask the rest of the questionnaire according to gender. You just have to specify in the programming instruction of Question 1: if R1 then Q10 :

Programmable survey online

So and if the interviewee answer he is a man then Q10 question will be prensented to him.

According to this mecanism you can compute any survey.

Inside the solution here is a compiler that analyse the instruction to determine next answer to ask to intreviewee.

Isn't taht fun! 

Migration to Visual Studio 2019 Community

I did upload the project and open the solution in Visual Studio 2019 with out any problem. We made one comit very light a tag bad endding then it was all.

The most difficult thing in this case was the database connection string of course ! I was quite sure that it will be impossible to open DB ASPNETDB and QuestionnaireDB into the SQL Server installed with Visual Studio Community 2019. There was no problem at all.

So with Visual Studio 2019 you can dowload the project, open and compile while running you will get this error :


Survey Online - The user instance login flag is not supported on this version of SQL Server. The connection will be closed.
Survey Online - The user instance login flag is not supported on this version of SQL Server. The connection will be closed.

We are searchint for a solution, Follow Us on GitHub : ASP.NET SurveyOnline

See you there!

The solution seams to be there : Upgrade .mdf files

No the solution is here :

LocalDB instances are all "User Instances", and there's no need to specify User Instance=true in your connection string, in fact it is not even supported (as you can see). Just remove this part and it's going to work fine.

Stupid chubby SqlServer !