>Hi all, I hope I can make myself clear...

If you have trouble explaining how the application work, maybe it's time to rethink the design.

Just with that single problem, you violated 4 rules that I have fixed myself:
1. Use grid only and only if it's the only control that make sense for the current situation
2. Relations are never based on values that the user can see. Use surrogate keys instead
3. Rarely use SET RELATION. Use views instead
4. Grids should be read-only. Use command buttons to display a separate form to modify records in a grid

HTH

>I have a grid with 6 columns, the first 3 are keys to 3 different tables and the last 3 display what the first 3 columns mean. Problem is, when I modify any of the first 3, the pointers or relations to the other tables move randomly, thus displaying wrong values in the last 3 columns.
>
>It also gives me an 'Record is out if range' error when adding records while on the grid. I keep recreating indexes, but somehow it keeps messing itself up.
>
>By the way, I've been having this type of problem with Visual, DOS worked great with many relations at once.