Macro generates some tables and then SendObject's them out to users in 2 parts (two different groups of users recving diff tables).
sendobject: tables A&B to users Al & Bob
sendobject: tables A&C to users Cindy & Deb
Is there some way to set this up so that the enduser can reply 'No' to the first sendobject call, and then still have the code continue to move to the 2nd sendobject call? no matter what i try, whatever code or parent macro has initiated the request gets shut down as soon as user replies "No" to the first sendobject task.