>>1) Use the grid builder, this then sets the relation between the two tables.
>>It seems in this case the tables don't have to be in the data environment.
>
>I would think that this adds them to the DE, doesn't it?
>
>>2) Put the tables into the data environment. Use drag and drop to relate
>>the tables (if a persistent one doesn't already exist). Drag and drop the
>>child table onto the form. The grid builder can then be run to set up
>>the columns (not necessary), but the relation is not set between the two
>>tables since the relation is set in the data environment.
>
>Sorry, but I lost you there. The relation is set, but it isn't?
>
>>A) Am I correct that these are two different methods, or am I confused?
>
>I think they are the same, but I confuse easily. :-)
>
>>B) Which is the best method?
>
>Well, when taken in conjunction with 'C)', neither is. Do you have the option of
>using a parameterized view?
>
>>C) I am using method 2, but I can't get the order of the child table in the grid.
>>RFID is the primary key in the parent table and RFID is the foreign key in the
>>child table. How do I set the child order.
>
>AFAIK, the child order needs to be the foreign key, or it won't work.
>
>>So... if anyone can lend a hand to a rambling numbskull, I would appreciate it.
>
>Parameterized, ordered views are the best way to go in situations like this.
>Something else that might work is to base the grid on a SELECT statement. If you
>need to edit in the grid, copy the results of the SELECT into a temp cursor. Just
>be careful that you don't lose the connection between the grid and the RecordSource
>when you do that.

Garrett,

Yup. I should have added in parameterized view, but I think that it is unecessary to use one.

Can you help with the problem.