I'm not clear on what is happening. I don't use the grid builder myself. When the grids RecordSource is set to a table or view and the RST is alias, and nothing else is set the grid columns follow the order of the fields in the table. You should then be able to change the Column ControlSouce to be a specific field. Also if you change the columns BoundTo to .F. you can override that again with the contained control in the column.

I'm not sure what could be causing it to not recognise or change the columns control source. Can you look in the debugger and see if the controlsource has changed?

BTW, I think the builder will automagically add the table to the forms DE behind-the-scenes.


>My DE is empty. I open all tables in code when the form loads. I do this because I store the path to the data in a variable, and I haven't had a chance to see if the DE can do this for me.
>
>You are right...it is placing the fields on the grid in the same order they are in the table. It does this without regard to my controlSource settings.
>
>I started over using the builder again (Barbara is laughing now) just to see how it works (not because I like wizards :)). It basically doesn't work. Matter of fact, if I try to omit the first field in the builder, the first field shows up at run-time anyway.
>
>It just seems to me that you should be able to use the tool to quickly create the grid, and that the tool should place its settings in the appropriate properties of each column. Then I could modify from that point.
>
>Why would Microsoft store these settings any other place but in the properties of the grid? It seems like that they would have gone to extra work to do it the way they did it, and it is less functional.