Access|select| Error |access|select
Too long did not update this blog, not do not want to write, but usually contact with the ASP programming is almost an endorsement of the state, there is no creative coder work, there is no new ideas, there is no sentiment, can not write Ah. Make Shida brother to remove my links are embarrassed to answer. First of all, say sorry to Brother Shida.
The point, these days after a small system to write, the process of writing or that is not creative endorsement-like. However, there is a strange problem when using it. The customer is using the English version of IIS in the English operating system. Program runs to Conn.execute (..) When incredibly prompt:
Selected collating sequence not supported by the operating system.
The delivery of the chest said my program is absolutely no problem, began to blush. Oh. )
Baidu search a bit, but also a lot of people encounter this situation. The reason for the error was found in one of Csdn's Questions (http://search.csdn.net/Expert/topic/799/799654.xml?temp=.6843073). On top of that, access is created in one language and used in another language to prompt this error, not exactly why (maybe, but my English is too bad to read.) )。 Knowing the big problem, there is a way to solve it.
To confirm the correctness of this statement, I wrote a simple dataconn file. Connect to the Access database I built, the error is not changed "Selected collating sequence not supported by the operating system.". When you connect to an access that is created in a system that is the same as the server environment, and everything is OK, this explains the problem. As for why. I still don't get it, but the goal is to get the system running.
My solution: Upload access to the server for normal use and then clear out irrelevant tables (because the database is in another program, so there are some tables left). Then directly use SQL to create the tables in my database into the current access. Now the system is working and the task is complete.
But I know that this approach can only be seen, and for authors of global shared programs, this problem will be a big hurdle and there should be a foolproof solution. It's just, I don't know. It needs to be solved ...
