Last post Feb 02, 2006 10:11 PM by Art1220
Feb 02, 2006 10:11 PM|Art1220|LINK
I find out that if you are using a case sensitive SQL setting to install the DNN, you would be 100% get some sort of the store procedure doesn't exist errors. When I tried to look into the problem, I found out that not only the case sensitive problems exist
in the original .SqlDataProvider files, one of the store procedure call GetLists is not even able to be grenerated because of the invalid column name DisplayName. I don't know if the core team is going to fix the problem or not, but this should be the problem
that need to be addressed on next release version.
Here is the fixed version of the SqlDataProvider files:
You might find out that after using this file to install dnn, some of the modules like Links might also have the same store procedure doesn't exist error. Those are also because of the case sensitive, so you can go ahead and change the .SqlDataProvider file
within that module to solve the problem by yourself.