sql server replication: Joe,
there is nothing out of the box to do this type of thing (the profile setting -SkipErrors applies more to transactional replication). You could of course create separate publications - one for the data and one for the troublesome procedures/views, which means that the time-consuming table replication is done once only. Alternatively the views could be applied as a Post-Script. Either way, the fact that there are errors in these scripts is worrying and would need addressing.
Regards,

Many times I can run snapshot agent to published a database sometimes
snapshot agent takes two hours to run. Snapshot agent snapped the database
fine, but when creating subscribers it failed because some views or stored
procedures has errors in it. I don't like deleting the stored procedures
and run snapshot agent again which takes up another two hours. Is it
possible for me to run any scan/check for replication errors/ subscribers
creation errors on the database before running snapshot agent so that I
won't waste so much time to find faulty stored procedures or views.????