><snip>
>Thanks for the advice I'll try that route next time; actually I was trying to take a route similiar to yours in my repoort creation, I first designed the report based on a View which contained the same fields as the Select statement I was going to use, in this way at design time I actually had access to all of the captions I had entered in the tables design. I was running into problems when I tried to break the report away from the view so it would read it's data from the SQL Select.
>
>-Preston

One advantage of using the 'Quick Report' to start is that you can use the alias name with the field or not, as you choose. If you put a table/view into the report DataEnvironment the report automatically adds the alias to the fieldname.