Steampunk Workshop

Found via Gizmodo.

'DropDownList' has a SelectedValue which is invalid because it does not exist in the list of items. Parameter name: value

Exception Details: System.ArgumentOutOfRangeException: 'DropDownList' has a SelectedValue which is invalid because it does not exist in the list of items.
Parameter name: value

I've got a dropdownlist whose SelectedValue is bound to a sqldatasource whose dataset is dependent on the selected index of another dropdownlist. By the time the SelectedValue is bound, the other dropdownlist should already have the appropriate selectedIndex bound. I know this is just a matter of timing, but it's pretty frustrating none the less. To see that feedback was given and summarily ignored is downright infuriating.

Response provided from feedback:
"Thank you for submitting this suggestion. From the brief description you've provided, it's difficult to determine what's actionable here. If this is really a suggestion, can you provide a more detailed description of the scenario and what you would like to see improved? If you're experiencing a problem with the product, can you resubmit it as a 'code defect' and provide repro steps along with any example code that would enable us to repro the problem. You also mention that Microsoft is aware of the problem - is there a KB article or exisiting bug that you can reference? All of this will help us to determine what needs to be done."

Wow. That is one of the Laziest responses I've ever seen. And don't think the lack of an individuals name went unnoticed. Lazy AND Cowardly.

I felt a little better after reading this, and resolved myself to a codebehind solution (for the time being).

Addendum:
No problem should be posted without a usable solution. What's the point in finding this if it doesn't help or at least point you in the right direction.

I'm currently working with Telerik Controls which I like a lot, but they're based on existing MS components so their combobox, for example, inherits the same behavior. Here is an example from their documentation which should cover a wide range of issues similar to this one.

SQL Server GRANT EXECUTE TO [Role] During Stored Procedure Creation

Why is it so troublesome to find the simple things?

For some time now I've wanted to automatically grant execute permissions to a specific database role during the creation of my stored procedures (for a given app). No, I don't want to grant permissions to a set of existing procedures. I grew accustomed to doing this when I created Oracle Stored Procs a few years ago and tried several times with similar syntax to no avail.
Well I'm about to create a sh*tload of pros and the extra time (and frustration) it takes to add and grant execute on each sp through the management studio was enough to get me to look for the solution again.

I already create enough procedures to warrant the creation of a temp txt file to hold a new proc template:

SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
GO
-- ==============================================================
-- Author: Brian H Donoho
-- Create date:
-- Description:
-- ==============================================================

CREATE PROCEDURE [dbo].[usp_]

AS

BEGIN



END

Looking here, the syntax is pretty much what I'd tried using at the bottom of the CREATE PROCEDURE.

Of course it was one tiny little thing coming between me and my goal. A couple of well placed GOs.

This Works:


SET ANSI_NULLS ON
SET QUOTED_IDENTIFIER ON
GO
-- ==============================================================
-- Author: Brian H Donoho
-- Create date:
-- Description:
-- ==============================================================

CREATE PROCEDURE [dbo].[usp_]

AS

BEGIN



END
GO

GRANT EXECUTE ON [dbo].[usp_] TO [Role]
GO

Buyers Remorse Trumped by Stubbornness

Portal Song Lyrics <-<- Reading = SPOILER ->->

This was a triumph.
I'm making a note here: HUGE SUCCESS.
It's hard to overstate my satisfaction.
Aperture Science
We do what we must, because we can.
For the good of all of us, except the ones who are dead.
But there's no sense crying over every mistake.
You just keep on trying till you run out of cake.
And the Science gets done.
And you make a neat gun.
For the people who are still alive.

I'm not even angry.
I'm being so sincere right now.
Even though you broke my heart
And killed me.
And tore me to pieces.
And threw every piece into a fire.
As they burned it hurt because I was so happy for you!
Now these points of data make a beautiful line.
And we're out of beta.
We're releasing on time.
So I'm GLaD. I got burned.
Think of all the things we learned
for the people who are still alive.

Go ahead and leave me.
I think I prefer to stay inside.
Maybe you'll find someone else to help you.
Maybe Black Mesa
THAT WAS A JOKE.
HA HA. FAT CHANCE.
Anyway, this cake is great.
It's so delicious and moist.
Look at me still talking
when there's Science to do.
When I look out there, it makes me GLaD I'm not you.
I've experiments to run.
There is research to be done.
On the people who are still alive.
And believe me I am still alive.
I'm doing Science and I'm still alive.
I feel FANTASTIC and I'm still alive.
While you're dying I'll be still alive.
And when you're dead I will be still alive.
STILL ALIVE
Still Alive...

Dism: Buying Love

You can't buy love, but you can rent attention.

Dism: Obvious

One person's obvious is another person's revelation.