I don't know how a macro can easily capture this in a condition. You can do
it more easily if you use VBA code. Or you can use a VBA function that is
called by the macro's Condition expression and that tests whether the object
exists.
But, tell us a bit more about why you need to use this code. Why wouldn't
you already know if an object exists before wanting to delete it? Tell us a
bit more about your setup and when / why you want to run this DeleteObject
step.
--
Ken Snell
<MS ACCESS MVP>
Ritesh said:
I have a DeleteObject argument in my Macro but i only want it to run if
the object is actually available to delete, otherwise i want to skip the
delete object argument and move on to the next agument.