Hi everyone,

I am trying to use DNN with several applications in Turkey. I want to tell development team about a simple fact about Turkish Alphabet. In my alphabet, the letter 'I' is not capital  of i . I've told this fact several times in that forum. But there was no benefit. I just would like to transmit that fact to development.

The letter 'I' is  capital of 'ı' and 'İ' is capital of 'i' in my alphabet. There are endless problems because of Dotnetnuke.SqlProvider.dll. If  you use @IsScalar as parameter and call back again as @isScalar . SQL raises an error flag! Same is valid for @Id and @id. Is it so hard to take care of these parameters? Lots of  friends of mine think that, DNN is useless in Turkey.

Yes, as I said, how can I transmit that fact to development team?Can anyone help me? Mr. Leupold?

Actually the problem is not related with db collation. Problem is with the windows regional settings. If you select your keyboard settings as English than there will be no letter like 'İ' or 'ı' then there will be no problem. But when you select turkish keyboard then it crashes. This is a very simple problem Mr. Leupold. There is no need a test bed. You just need to obey coding rules. If you want use a parameter called @IsScalar, you should call it as '@IsScalar' not like '@isScalar'..Thats all. There is no need for a test bed. And In my opinion, DNN will work well even on a DB with collation Turkish CI_AS.Because it is also CI_AS. But it has nothing to do with parameters named as '@IsScalar' when calling back  them as '@isScalar'..beacasue they are different parameters in Turkish.

Thank you very much for your interest..

Sebastian

I guess that he is talking about the real stored procedure named as "IsThisStored" and the name in dataprovider being "isThisStored". Differences in the I will cause problems for this language

Am I right?