I haven't updated this blog for a long time, I don't want to write, but the ASP programming that usually come into contact is almost the state of the book. There is no creative CODER work, no new intentions, there is no sense of understanding, no writing .. My link is not so embarrassed. I am sorry to this.
Question, I took a small system written in these days, the process of writing or the universityless backbrama .. However, it encountered a strange problem during use. The customer is used in English operating system English version of IIS. When the program is running to conn.execute (.): Selected collating sequence not supported by the Operating system. (When the chest is checked, I said that my program is absolutely no problem, I started blushing. Ha ha.) Search with Baidu There are also many people who encounter this situation. Among them, the cause of the error prompt is found in a question of 9CBS (http://search.9cbs.net/expert/topic/799/799654.xml?temp =.6843073). As mentioned, Access is created in a language, and in another language will only prompt this error, and if not say why (maybe it, but my English is too bad. I don't understand. . If you know the problem, you have a solution.
In order to confirm the correctness of this statement, I wrote a simple Dataconn file. Connect to the Access database, the error prompt, change "Selected Collating Sequence Not Supported by the Operating System.". When connecting an ACCESS created in the same system as a server environment, there is no prompt, everything is normal, which explains the problem. As for why .. I still didn't understand, however, this purpose is to let the system run.
My solution: Upload the access to the access to the server and turn off its unrelated table (because this database is in another program, so there are some tables). Then use SQL to create the table in my database to the current Access. Now the system is running normally, the task is completed.
However, I know that this approach can only see the tricks. For the authors who publish the global sharing process, this problem will be a major obstacle and should have a full solution. Just. I still don't know .. Say to solve ...
Now what is going on now. It turned out to be the reason for "database sorting order". I just saw Access's settings, the default is "Chinese Pinyin". The location of the "Database Sort Order" in the Chinese version is Tools -> Options -> General -> New Database Sorting Ordered to "General" After the new database will resolve the problem.
