I've inherited an application with a SQL Server 2005 database and both
a new PHP web-based frontend and an older, deprecated C# 2.0 Windows
frontend.  Most people use the web frontend now, but there are a
sizable number of stubborn users who would rather switch applications
than abandon their Windows client.  The app uses practically no
bandwith or disk space, so it's hosted on one of those cheap IIS
shared hosting accounts, that just happened to allow direct logins to
SQL Server for the Windows clients.  But that host just decided it
would restrict SQL access to local connections only, so while my PHP
frontend still works, the Windows clients are now without service.

Does anyone know of an inexpensive shared IIS/SQL host I could switch
to that allows external connections to SQL?  I'm assuming that's
pretty much a long shot in this age of (justified) security
paranoia....

So if that's a "no", my real question is - is it possible to get
around this using some sort of raw web interface to the data (most
likely from ASP.NET), so I can modify the C# code to retrieve/post to
that instead of using a connection string like it does now?  I'm
proficient in C#, but don't know much of anything about ASP.NET, Web
Services, or WCF (or if those are even applicable), so a pointer in
the right direction would be much appreciated.

Thanks.
-Eric