Can you please provide more information?  I think this is possible but without knowing what you are attempting to accomplish it is kind of hard.

You can build loops that perform...

What about reviewing the data after the submit has been issued and before the data is passed to convert the & to a different character and then convert it back...

You will need to build a table with current passwords and a historical table with same data.  The password field will need to be encrypted.  You will then have to...

Or jokingly you could contact the makers of the product (see attached link).  They might have a nifty wizard to help you

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=120&messageid=109456

Backup log should be however, I think that DBCC SHRINKFILE will be noticed as this may prevent new records from being written to the log while it is running.

I would research using an in-line function.  You cannot call a stored-procedure from a SELECT but can call functions.  The BOL has decent information on UDFs

I believe FSO uses alpha sort.  If you need to use a different sort you will need to use a folder collection.  Loop through all the files in the collection...

I did contact them and they have requested some bounce e-mails from people I know had e-mail returned.  I did not contact you because I am sure the sheer volume...

Have not run across this however, I know that when I installed Reporting Services and all samples it created the AdventureWorks DB

Collation is defined (beginning with SQL 2K) at the Server, Database, and even columnar-level.

Easiest fix (because it is your test server) is to dump the database and recreate it with...

Another way to do this would be

WHERE Comp_id IN (1, 2)

Why not WHERE DATEPART(MONTH, CompareDate1) = DATEPART(MONTH, CompareDate2) AND DATEPART(YEAR, CompareDate1) = DATEPART(YEAR, CompareDate2)

?  Of course the varchar > varchar compare would be better execution-wise but the above code should...

take away SELECT from the tables and views.  Force everyone to use stored-procedures that are installable by the DBA team only.  This will ferret out all of the rogue databases. ...

Another thing you may need to research are indexes and keys.  I seem to remember something about not being able to insert records unless there was a key.

Another thing to keep in mind is IF you are writing this inside Crystal Reports it will be a pain to maintain (know from experience).  Why not write this as...