A potentially dangerous Request.Path value was detected from the client (&).

I've looked this error up and tried fixing it for quite a while but am still stuck.

My .NET app, passes a filepath name to a Javascript function that I created, which then passes the path to a Flash audio player to play MP3s. This works fine except for when there is an ampersand in the file path.

After reading, I learned to try adding the following to my page directive: ValidateRequest="false"
This didn't work, so I tried adding it globally in web.config, like so:
<httpRuntime requestValidationMode="2.0"/>
<pages validateRequest="false" />

'&' is supposed to be used as a query string separator and spaces are supposed to be urlencoded as '%20'. While they may be valid on your machine, they are trouble on the web. I always remove spaces from filenames and paths and would not use an '&' in them either.

Popularity Can Be Measured
Sometimes we deal with questions of popularity, and we need a way to collect opinions from our clients. This article shows a simple teaching example of how we might elect a favorite color by letting our clients vote for …

Introduction
This article shows how to use the open source plupload control to upload multiple images. The images are resized on the client side before uploading and the upload is done in chunks.
Background
I had to provide a way for user…

Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…