Hi Dan,
The reason for not using a subform (set to datagrid) is that in fact I am
trying to resolve a problem for which I failed to get a subform to work. I
am actually building a system for creating some pretty complex price lists
where the user detrmines how many price columns he / she wants for each
given range of products, and sets the name for the column. Each column has a
GPM set, and so it effectively becomes a straight calculation from the
purchase price. Each column is given a priority (supposed to be used for
displaying the columns in the correct order). In order to actually do the
calculations and display as price columns I use a cross-tab query (which I
dump into a temp table so the user can actually make changes, and the
changes are only updated to the database when the save button is pushed).
Unfortunately, the only way I could find of displaying the columns in the
correct order was to concatenate the priority field with the users name for
the column. Add to this the problem of not knowing in advance how many
columns each product range will have applied to it, the only way I could see
of using the standard datagrid control would be to over-estimate how many
price columns are likely to be used, and then somehow to hide columns that
are empty (which I may well have to resort to, but goes against the design
concept of offering the greatest flexibility).
I really don't know if the datagrid control will actually help resolve the
problems here, I just wanted to explore the possibilities (and I figured the
user would at least be able to manually change the order of the columns so
that I could take out the priority field concatenated with the column name).
Sorry for the wordy reply, but I do hope this helps you to understand my
motives for looking at an alternative to simply building a standard subform.
Thanks & Regards,
Paul