>>>>>Pls note that these are multiple Items for a single order/invoice, that is why i've kept data entry in grid..
>>>>
>>>>Great - you can only be working on one line at any given instant.
>>>
>>>Pls advs. if there is any problem using grid, because i'm not able to understand, what exactly you mean..
>>
>>It's a different philosophy on what should be done in a Grid - using a separate frame for data entry done on the currently selected record in the Grid, that doesn't have the context shifting issues of a grid, works better for me. YMMV. Good luck with your problem.
>
>Ed - Generally subscribe to this theory as well. I have to be dragged kicking and screaming into letting users enter data into a grid. But sometomes its absolutely necessary. I have a couple of applications where the data entry is spreadsheet-like... the user has to be able to arrow down and around quickly to cut and paste values. In all cases, however, I have managed to do all of the ADDING records beforehand, and so I don;'t have to deal with autoadd and so on.
>
>IOW, I think this strategy is sound, but there are exceptions to every rule, and it could very well be the case that Vinod has one.

Using a grid to emulate a spreadsheet certainly is a possibility; I don't consider multi-item entry for an invoice to be one of those things that has this particular need, but I'm not the be-all and end-all of UI implementation (I have clients who pay me to do their system designs, and pay more if I promise to keep my hand out of the UI design! < g >) IAC, the Panel, PanelLink and Partition properties are probably the keys to accomplishing the desired effects of having one or more columns that don't scroll when other columns do...