>If it is okay with you, I would like to learn from your experiences with accounting apps and apps in general.

Please, don't consider me an expert in accounting, or accounting software - I am not. I am still confused with all the details in an accounting system.

> ... Like I said that there are 3 parts as per my observation in an Invoice, so it is for Purchase Bills, Sales Returns, Purchase Returns.
>
>What I would do, when I expand our ides into an app, is to map the values that are there in the Grid with similar valued records in a General Journal table which will then be used for reporting purposes. This is the case in my current DOS based app which has all the part 3 values as fields in the sales table.
>
>Now that we are thinking in terms of a grid for part 3, that means that already the values are row wise. Can this General Journal and Part 3 Grid (for all modules be it Sale, Purchase, J.V., etc.) now be one and the same or will it have pitfalls?

Especially if the structure in two tables is quite different, it is usually better to use separate tables.

>
>I hope I have been able to explain what is running in my head. Something like.
>
>Sales Header table ... Sales Items table ... Part3-GenJour table
>Purcahse Header table ... Purcahse Items table ... Part3-GenJour table
>Journal Voucher Header table ... Part3-GenJour table
>
>But the only problem I foresee is that in my current DOS General Journal table I have Debit and Credit columns for values, in our Grid case there is one column for values.

I found it convenient to have Debit and Credit in separate columns. It is quite possible to put it into a single column, to save space, but that makes the programming more complicated.