Took a day and a half, but I got the exec spusp_GetConfigParamValue 'MYAPP','MYPARM', 'STRING', @MYVALUE sql task to work:
1) kept isstoredproc as false
2) on parameter mapping, said output datatype was object
3) in the proc definition, said output was a sql_variant, not a varchar(255)

I found that I also had to change the type from ADO.NET to OLEDB on the EXECUTE SQL Task

However, I then found this other link

http://blog.boxedbits.com/archives/8

Which allows you to use a script to populate all variables from the parameters table. (Only works for Strings. However, Strings is not much of a limitation as most of what we usually want to change are file paths, server names, etc. The other limitation is that the vars must already be created. I am looking to see if there is some code that will create the vars, ideally at global scope.)

Regards


Paul Simon

http://blogs.msdn.com/mattm/archive/...arameters.aspx

This page explains the different settings for different connection types very well.

I looked back in the book and noticed that it was clearly stated in step 4 on page 149 to use "ADO.NET", that was my problem! The default is OLEDB and so I didn't pay attention.

I wonder if many of you did not miss the same thing because many of your solutions involving changing to OLEDB but you don't have to.

The original example in the book works fine.

Under General:
ConnectionType: ADO.NET
SQLStatement: EXEC usp_GetConfigParamValue 'MYAPP', 'MYPARM', 'STRING', @MYVALUE OUTPUT

Under Parameter Mapping:
VariableName: User::myFile
Direction: Output
Data Type: String
Parameter Name: MyValue
Parameter Size: -1

And that is it.