Maybe it's because of the CamelCase object names. ISTR that lower case 
was fine without quotes but upper case and camel case had to have quotes 
because Pdox object names defaulted to lower case. Not 100% sure but 
give it a try. Maybe you flipped a "insensitive compare" switch?

Peter wrote on 8/11/2018 10:23 AM:
> I have a form that has been working just ducky for many years. Today I 
> had to make some simple changes which went fine. Upon pressing [F9] for 
> syntax check, pdox started balking at any code reference to objects that 
> did not have quotes.
> 
> eg codeline: fldJobs = tbfMainSched.recSched.ApptNote
> Pdox highlighted ApptNote and the status bar msg was "Error: object 
> expected."
> I put quotes around ApptNote, pressed [F9]
> Then Pdox highlighted recSched and put up same error msg
> I put quotes arounf recSched and then everything was right with the 
> world again.
> 
> q1) aren't quotes optional, just for readability?
> q2) why has this been working for so many years and now suddenly Pdox is 
> complaining (I have always had compile warnings/debug turned on, always)
> 
> Thank you for any insight
> 
> Peter