I haven't updated this blog for too long. I don't want to write it, but I have almost always been an endorsement of ASP programming. I have no creative coder work, no new ideas, and no feeling, it cannot be written .. I am so sorry to say that I have removed all my links. Sorry for this.
The question is: I have written a small system over the past few days. The writing process is still the uninspired endorsement. However, I encountered a strange problem during use. The customer uses the English version of IIS. When the program runs to conn.exe cute (...), it prompts:
Selected collating sequence not supported by the operating system.
(When the delivery was done, I patted my chest and said that my program was absolutely okay. I started to blushing. Haha .)
I searched through Baidu, and many people encountered this situation. One of the questions in csdn? Temp =. 6843073. In general, access is created in one language, and this error is prompted only when used in another language. Specifically, it does not mean why (maybe, however, my English is too bad to understand .). Knowing how big the problem is, there is a way to solve it.
To verify that this statement is correct, I wrote a simple dataconn file. Connect to the ACCESS database I created. The error prompt will remain "Selected collating sequence not supported by the operating system .". When the Access created in the same system as the server environment is connected, the system does not prompt that everything is normal, which indicates the problem. As for why... I still don't understand, but this time the goal is to let the system run.
My solution: Upload the access that can be normally used to the server and clear its irrelevant tables (because the database is in another program, so there are some tables left ). Then, use SQL to directly create the tables in my database into the current access. The system is running normally and the task is completed.
However, I know that this method can only be used for recruitment and recruitment. For the authors who release the global sharing program, this problem will be a major obstacle and there should be a comprehensive solution. But I still don't know... I have to solve it...
Now let's figure out what's going on. It turned out to be the reason for "database sorting order. I just checked the access settings. The default value is "Chinese pinyin ".
The location of "database sorting order" in the Chinese version is
Tools> Options> General> sorting order of new databases
Change to "regular" and then create a new database to fix the old data.