SQL Server - Ignoring object dependencies to copy a DB (despite some column referenced in a stored procedure no longer existing)
As others have said, you have problems which are goign to require serious re-evaluation of how you do business.  You can keep patching things with virtual duct-tape, or you can come up with a plan to fix the problem.

However, a duct-tape solution for this particular problem would be to check for the existance of those columns first (using information_schema.columns), and then create the appropriate version of the stored procedure (or not at all).  This will continue to create havoc, but it will at least buy you some time.