Marked as solved; where the resolution was to just stop using DoCmd.SendObject altogether.