Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Advice on General Ledger design
Message
From
02/04/2004 22:34:55
 
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
00885098
Message ID:
00891956
Views:
21
Don,

I had that problem (only one field for the amount with +/- figures, or two fields one for DB and one for CR) for several years. Actually is not a problem, it's a design decision. The final user won't notice the internal structure as you will translate everything to the doble entry accounting method.

As I told you, after several years going around with both methods I decided to go with the two-fields way just for simplicity on the programming side. I think you need less code to manage this table structure.
Besides, if you are not an accountant I would go with the two-fields method. If you use the one-field you will spend more time figuring out the meaning of the transaction as the + or minus sign has to be added to the nature of the account (asset, liability, cost or income). I have spent many many hours on accounting exercises both at the university and at work, and I still have to think twice some accounting movements. I think it will help you understand your code and accounting if you have two columns, same as when you hand write it (almost nobody keep written accounting in one column with +/-).

HTH,
Javier.

>Cindy,
>
>Re: It would be simple to create a view that divides the amounts into DBs and CRs to use for display.
>
>I'm moving forward slowly on this project. I am a total neophyte with accounting but am a decent foxpro programmer.
>
>If I have plus and minus amounts in one field in a transaction table, I get a bit lost in figuring out if it's a DR or CR, depending on the account type. What would your recommend as the "simplest" setup to get the view your mentioned in the posting above?
>
>Any help is most certainly appreciated!
>
>
>
>
>>>Users prefer to "see" DB and CR columns; on forms and reports.
>>>
>>>"Internally", you could use a single field ... However, you have to weigh the effort it will take, from a programming POV, to constantly be "converting" from a single field to dual fields for display purposes.
>>
>>It would be simple to create a view that divides the amounts into DBs and CRs to use for display.
Previous
Reply
Map
View

Click here to load this message in the networking platform