Database error "The sort order differs from the system one": how to fix it?

As a rule, the majority of users who detect an error in the system indicating that the sorting order differs from the system one, apparently work with the package "1C" version 7.7. It is the one that is most vulnerable, not even in terms of the impact of viruses, but also in the area of errors and failures that lie in the code itself of the package. However, when an error message appears saying that the sort order differs from the system order, you should not panic. There are a few simple solutions that help to eliminate this problem quickly and permanently. In this case, you can apply two solutions at a minimum.

Database error "The sort order differs from the system one": what's the problem?

The problem is that the main program in the form of an executable file on the server or client machine can not initialize the database (SQL).

Because of this, the connected user (child) terminals can not access the database itself (although the main kernel of the program runs without problems). It is believed that access to the application itself is provided at the server version level, which is responsible for connecting other user computers located on the local network. With her, it is just the problem.

Further, solutions are offered that allow to eliminate this failure. Consider two basic methods that any user or novice system administrator can learn.

The sort order differs from the system order (Windows 7). What should I do first?

It is believed that in the release behind the number 26 was included the ability to ignore the database files. But do not rely on this service.

Non-existent object

It happens that the application at startup refers to an allegedly non-existent object in the form of the file OrdNoChk.prm, which seems to be located in the BIN folder of the program itself, installed in the program files of the system.

If there is a system message that the sort order differs from the system one, there is nothing easier than creating in this directory an empty file with the same name and replacement when saving, for example, in the same "Notepad" included in the standard set of any Windows -system. Here the question is also that the standard text editor of the settings containing the initial data, when it is directly edited and then applied in action, does not work.

Change the structure of databases based on local data exchange

On the other hand, the problem that a failure occurs with the appearance of a message that the sort order of the installed one differs from the system one, can be solved even by means of the program itself.

But here you should initially think about how useful it is to use the described tools and tools.

If an error occurs, when it is reported that the database sorting order differs from the system one, in the "1C" application you should select the configuration section in which you need to go to the administration, the code page of the IB tables and the point of the current system installation.

Conclusion

In principle, the message that in the "1C" database the sorting order differs from the system one, you can delete it completely (or get rid of it forever). As practice shows, in the simplest case, you can simply create an empty object, as indicated above. After that, an error indicating that the sort order differs from the system order will not appear any more.

In fact, only these solutions eliminate the problem. The fact is that in the "1C" environment you can write scripts or create additional applets to manage the entire system based on the same Visual Basic language using DVB format databases. Otherwise, the error associated with the appearance of the message mentioned above, will be eliminated quite simply, if you do not take into account the shortcomings in the code of the program itself or the virus effect. But this, I think, is not the worst thing. Sometimes the "curvature" of users who do not know how to organize a database and connect it to an installed program can lead to the error of this type appearing again and again.

Also, you should pay attention to the fact that when the automatic exchange of data of the platform with other databases is enabled, all of them should have absolutely the same encoding. If it is not installed for all databases, respectively, the very issue of importing and exporting data becomes, to put it mildly, meaningless. In extreme cases, as mentioned above, the encoding should be disabled. Especially this applies to situations where different versions of Windows are installed on different terminals, and even with different architectures. This can also lead to unpredictable consequences, up to the point that it will be impossible to work with the program with regard to simultaneous access to information.