Existence checks are an unavoidable circumstance to prevent errors. Unfortunately they not only blow-up the code but are also ugly, specifically when On Error .... statements are used. Over time I've compiled all I needed and made them as robust as possible. It became a proper module, last but not least due to the integrated existence check for an open Workbook which considers any Workbook open in any application instance. An existence check for an open Workbook for instance will always look like:
whereby <wb> may be a Workbook object or a Workbook's name.
Some may ask now himself: Why may it makes sense to check the existence of an object? The answer is that it can happen that an object had been assigned which meanwhile no longer exists. May it be a Workbook meanwhile closed or a range pointing to a cell of which the row had been deleted meanwhile. Cases like this are a source for really ugly errors which easily can be avoided.
The following has to be copied into a new Standard module e.g. named mExists (the coding scheme may easily be extended for other existence checks):
Bookmarks