"Chris Scott" wrote in message
What could be wrong with it and how would I go about repairing it?

I've only had a quick glance at this but I notice your un/protect
stuff. Be aware since 2013 that takes a long time. If that's what you
have try same without any protection and go from there.

Regards,
Peter T

I recommend setting the UserInterfaceOnly protection option at each
startup so code can make unrestricted changes to locked cells. Startup
reset is necessary because this option doesn't persist between
sessions. (Not to mention the PITA that toggling protection during
runtime is!)

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion