Help configuring a Cisco RV082 Dual WAN VPN router/gateway with a Cisco ASA-5510.

Thanks in advance for your help!

I have a problem and Cisco can't seem to help me figure it out....
What I am trying to do:

1. Using two external T1 internet connections that come from two entirely different service providers.
2. Bind those T1’s together using the load balancing functionality of a Cisco RV082 dual WAN VPN router/gateway.
3. Place the RV082 in front of a Cisco ASA-5510 that is currently in place and managing DHCP, Firewall security, NAT configurations and PAT into a LAN of roughly 50 end users.

more info:
In 7 months the contract for the WAN-1 service provider is ending. We brought the connection for WAN-2 in to prep for that contract end date and to take advantage of a really good price.

I really want to increase our speed around here. Offloading some traffic heavy services like FTP to a different WAN away from but still internally accessible to my end users. I thought this was an easy solution and a fun project. Instead it's turned into a mess!
If the above is just some crazy dream of mine that only makes sense to me please let me know.
I am open to any suggestions, besides giving up. ;)

Who is Participating?

>I have a wide span of external IP addresses that NAT or PAT through the ASA-5510 to private IP's of different web servers and FTP servers
This is going to be the biggest challenge for you. As akahan alludes to above, you need a transit network between the LAN on the RV082 and the WAN port of the ASA. This will probably have to be a private network.
You will have to let the RV082 do the natting from public to private. You can create multiple 1-1 static nat's on the RV082 that correspond to static NAT's on the ASA. For example:

You haven't said what the problem is. Which part of this isn't working?

You would want to set the outside interface of the ASA5510 to a LAN address on the RV082's LAN side (after changing the RV082's default LAN address to something other than 192.168.1.1, e.g., 192.168.0.1, so it doesn't conflict with your existing LAN on the LAN side of the ASA.)

By the way, you mention that "Outside Interface === (currently bound to WAN-1 @ 216.205.208.138-)," but it should be bound to 216.205.209.138 (see the typo?) If that's accurate, no wonder nothing's working!