Thomas S. Dye writes:
> Thanks for your response.  

No, thank you — because it turns out that org-reload didn't do the right
thing in your case (i.e. after an org-reload, you'll see that pesky
"N/A" again).  Here's a patch to fix that.