Version 1C: Enterprise 8 is rapidly conquering the market of software products to automate accounting, tax, operational records, as well as calculation wages. Hikmet Ersek is likely to increase your knowledge. To replace the version of 1C: Accounting 7.7 to a more modern 1C: Accounting Enterprise 8. Configuration 1C: Trade Depot changed 1C: Trade management with broader functionality. Meanwhile, many users are in no hurry to move to the new version and successfully use the 1C: Enterprise 7.7. That there are many reasons, but I think the main two: 1.Konservatizm: it is always difficult to get used to something new, give up the habitual way of thinking and work; 2.
configuration forces programmers 1C: Each company has its own specificity, which is inevitably reflected in the automation tools and accounting. Sometimes used in enterprises configuration 1s processed beyond recognition, as compared with standard versions. A new version means that virtually all the improvements will have to play by the new. Costs in this case simply enormous. Time goes on, day after day in the program are introduced and new documents, and the size of the knowledge base grows. The most conservative estimate the size of the information base for 5-7 years, grows to about 5.6 gigabytes. C such volumes of data 1C: Enterprise 7.7 simply can not cope. Periodic failures, partial loss of data and it’s only the beginning.
There is a risk in one day is not a total loss of data. Implications describe it is not necessary, it’s just a disaster! What to do in a situation where the transition to a modern version of the 1C does not seem economically feasible, and the directory information base continues to grow? There is a way. For any typical configuration 1s (such as 1C: Accounting, 1C: Trade and Warehouse, 1C: Salary and Personnel, 1C: Production + Services + Admin), there exists a mechanism of so-called “convolution base.” The meaning of this operation is as follows: for selected date (for example, on December 31, 2009) program gathers the remains of all parts of the records – stock on hand, cash balances on hand and in current accounts, balances of settlements with suppliers and customers, data on depreciation, etc. These balances are entered into the program on Jan. 1, 2010, and then all of the documents prior to January 1, are removed. Process itself is almost 100% automated. Previously backed up database in case something suddenly goes wrong. Upon completion of the convolution of the data in new and old information databases are checked. If the data match, process was successful and a new base can continue to use a few more years. Additional problems begin where the configuration is far from its original state. But this is not a reason to give up. For the experienced Programmer 1s similar problem only takes a few hours. As a result, we have a base no larger than 70-100 megabytes, and can be confident in the stability of the future work program of 1C: Enterprise 7.7. Whatever it was, the cost of convolution of the database simply not comparable to the costs that would incur in the event of complete or partial loss of data. All the best!