>In general, it looks OK.

Thanks.

>Like you, I also use fields of type "Currency" for quantities - but make sure that you won't need more than 4 decimals. Otherwise, you may want to use type "Double". In computations with Currency, all results are converted to Currency - which may give you some rounding errors. This can be avoided using mton() in strategic places.

I'll study mton() and how I can get it used in my case. Anyway I use a custom class for currency fields where the inputmask changes as required by the field, ie. if comment contains the word qty. the inputmask is 9,99,99,999.999, if word amt 99,99,99,999.99 and if word is rate 99,99,999.9999

>
>Isn't the invoice related to a sales order? I have the impression you are missing a FK to the related sales order, in the invoice header.

Yes related in a seperate way, ie not directly connected but through this middle file. One invoice can contain many orders per item and also in future I will have to allow for partially attachments with order, ie. 2 order of item a for 100 each, 1 invoice of item a 50 qty but 25 to 1st order 25 to 2nd order.


Thanks for responding. What I got from your response was what I was looking for. I wanted to know if my understanding and it's table data creation were in the right place. Also if this middle table business was the right solution.

Just in case you are interested I had put in code on one of the thread for a Table Builder couple of days back. Helps to create the initial table creation in a DBC using browse window. I had to setup a table yesterday night with quite similar fields and the creation was wasy as I could copy paste between records the comments and inpuitmasks, etc.