Several methods for designing a credential database in accounting computerization software (superficial)

Accounting Computerization replaces the inefficient manual accounting method and is the transformation and update of accounting technology. The correct establishment of the Credential database structure is the key to the design of Accounting Computerization software, because all accounting information is input and further processed through it. We have studied most of the accounting computerization software and found that its credential database has a variety of structures, and has its own strengths in further processing. Below we will discuss the design of several credential database structures with our colleagues. The description below only discusses the key fields, and the programming language uses foxpro2.5. The first design method is the database structure: field field name type width decimal field meaning 1 RQ date 8 date 2 PZH character 6 creden number 3 ZY character 20 abstract 4 kmh character 11 accounting subject 5 JF number 12 2 borrow amount 6 DF number 12 2. credit amount... after this design, it is more convenient to calculate the account balance. You only need to calculate the credit amount. The program design is as follows: Sum JF, DF to jfhj, dfhj for kmh = accounting account current account balance = previous period balance + JFHJ-DFHJ but we have trouble finding the other account, we need to agree that the first record of each credential is the borrower who borrowed the multi-loan credential or the lender of the One-loan Multi-loan credential, and when a one-loan credential appears, we also need to divide it into two records for storage, occupying disk space. The second design method is the database structure: field field name type width decimal field meaning 1 RQ date 8 date 2 PZH character 6 creden number 3 ZY character 20 abstract 4 kmh character 11 accounting subject 5 fx character 1 amount direction 6 je number 12 2 accounting amount... After this design, when calculating the account balance, you only need to calculate the credit amount, but the program design needs to change as follows: Sum IIF (FX = "J", je, 0 ), IIF (FX = "D", je, 0) to jfhj, dfhj for kmh = accounting subject, then: current period balance = previous period balance + jfhj + dfhj this design method has the same problems as the first method, but it is more innovative than the first method, by adding a loan identification code (only one digit) and reducing the value field (12 digits), this is very important for small-capacity disks. The third design method database structure is: field field name type width decimal field meaning 1 RQ date 8 date 2 PZH character 6 creden number 3 ZY character 20 abstract 4 jfkmh character 11 debit accounting subject 5 dfkmh character 11 credit accounting subject 6 je number 12 2 Accounting amount... After this design, when calculating the account balance, you only need to calculate the amount of the lending credit, but the program design is troublesome and needs to be changed as follows: Sum IIF (jfkmh = Accounting Account, je, 0), IIF (dfkmh = accounting subject, je, O) to jfhj, dfhj: current period balance = previous period balance + JFHJ-DFHJ this design method if we want to find the other side of the subject is relatively easy, jfkmh of the other side of the subject is dfkmh, and vice versa. In addition, when a credit card is used, we do not have to divide it into two records for storage. It is enough to use only one record, saving disk space. We also found that some database structure designs are cumbersome, which is not conducive to further data processing. We will not discuss them here. These design methods have an impact on the processing of input creden。 (such as accounting and checkout). Which database structure should be applied.