>>I've seen you code partially.
>
>>In your DE, you didn't established the relationship between jvhdr and jvdtl. >You can do it by connecting jvno field of jvhdr to jvno order of the jvdtl >temporarily then click the connection object to edit the relationalexpr >property. make dtos(jvdate)+str(jvno) instead of jvno only.
>
>>Another suggestion is that, instead of using a compound index, add another >field which will contain unique values on both table and use it for >connection. Use SYS(2015) to generate unique value for you.
>
>I had set the properties for the grids linkmaster & relation expression.
>If I use tlkey from the transaction tracking instead of sys(2015) will that be ok.

I prefer establishing relationship in the DE rather than directly in the grid.

It's alright! As long as you could establish relationship without using compound index although I'm not saying that it's not allowed. This way, you can get rid of jvdate and jvno in jvdtl if you want.

>Here actually the jvdtl file holds the data so I want to get rid of jvhdr. But
>the VCR buttons for navigation whould also work. The same structure was used in my old FPD2.6 package.

If you do that, you're breaking the rules of normalization. Don't make a shortcut to solve this. 2 tables is more flexible long term. What if you need a remarks or description later on that describe the whole transaction and not on every detail?

>Is the code any good or does that require to be radically changed.

Improvements is a better term.

>(How to get the original message for replying in UT. I have done this manually.)

The feature is for Premier UT members only.