It would be great if we could isolate SubQuery Columns from other Columns, I find that as I use Stored Procs, the field names match the main query field name alot of the time. This gives the wrong info, and forces me to use 'fake column names' or not use sprocs.

Perhaps a format like: [ColumnName,SubQueryName]

Main query columns are just : [ColumnName]

For instance:
{SUBQUERY, Name="qryLinks",
Query="EXEC MyStoredProcedure [UserID]",
Format="<option value='[ID,qryLinks]'>[MainQueryColumn]-[Label,qryLinks]</option>",
SelectedFormat="<option value='[ID,qryLinks]' SELECTED>[MainQueryColumn]-[Label,qryLinks]</option>", SelectedField="ID",
SelectedItems="[ddID]"}

In this manor the values would be from the SubQuery, but the option text could include columns from the main query.

Thats odd, I will have to double check the Sub query, it was in the original specification to work exactly like you just posted. It is supposed to simply piggyback the logic provided within the Execute Action logic.

I have been having trouble using any resulting columns at all from a stored procedure when i use it in a subquery. If my subquery is as follows:

{SUBQUERY,Name="qryRating",Query="Exec ProductRating [ProductID]",Format="[ProductRating]"}

and the last statement from the Stored procedure is "select AVG(Rating) as ProductRating from Products where ProductID = @ProductID

Then why does the resulting output just have the literal text, [ProductRating] ? Maybe I'm just doing something wrong ... can someone please help.

Thanks

Nevermind ... I had to clear the web cache. After I did that it worked.