I had thought of that and made sure that the table is always selected prior to running the report. I've even had this occur when I was creating an on-the-fly report with only one table open. I cannot find any reason or rhyme to the behavior but it is VERY frustrating!