I have used the free version of DynamicPDF from ceTe Software for many years without any problems ;)

http://www.youralarm.com - written in ASP.net & SQL Server

Well, if you are unhappy with DiscountASP then I think you are in for a tough time. I have been with them for over 5 years and their servers have a very high availability.

http://www.youralarm.com - written in ASP.net & SQL Server

Yes, there are a small number of tables that would have new rows written into them but it is acceptable and we can do a manual transfer of the data some time after the recovery.

http://www.youralarm.com - written in ASP.net & SQL Server

This has nothing to do with the web provider. I have been with the provider for years and the database has never failed in all that time. Is it not reasonable to expect that they do service pack upgrades on the database as they become available ? No provider can gaurantee 100% uptime, but unfortunately in the business that I'm in - I have to. So, even though I have never had a database crash, that doesn't mean that there won't be one tomorrow. As my MS Access database is stored on the web server and not the database server, it seems like a good way to keep things going in case the database server is unavailable.

http://www.youralarm.com - written in ASP.net & SQL Server

I run a web application that relies on the database being up. Under normal conditions my ASP.net app connects to my SQL Server database, however, my web host occasionally takes the database server down for maintenance leaving my main app without a database. I have created a duplicate MS Access database so that it can run things temporarily if the SQL Server is down. Does anyone else do this, or something sililar in order to achieve "poor man's database redundancy" ? If so - at what stage do you check for availability of the SQL Server ?

http://www.youralarm.com - written in ASP.net & SQL Server

Guys, I have a NAT traversal issue that I need to solve using VB.Net and I can't do it with the .Net socket class. Here is an overview.... Remote client sends out a UDP packet from its internal IP on port 1234. The NAT router maps it to the external IP plus a mapped port (let's say 9999) My UDP listening software picks up the packet and I am able to find out the IP address and mapped port number (source port). The problem with NAT is that if I do not send a packet back from the same source port - it will be rejected (symmetric NAT). So, in my VB/net app, I connect and send back a response as follows.... udpClient.Connect(RemoteIP, SourcePort) 'code to send the packet goes here I use Ethereal to view the packet going out and the destination port is 9999 as expected, but the source port of the response gets mapped to a different port number. So, even though the packet hits the correct remote router port, it gets rejected because it came from a different source port. My question is, what hardware device is mapping the source port of my packet and how do I stop this from happening - or work around it ?