I think I found the problem. It's NOT the path nor the procedure file name, it's the way Foxpro interpret class definitions in a PRG file.
If I added a dummy function at the top of CALENDARCLASS.PRG, the whole thing worked! I actually suspected about this, but I was distracted by something else after started this thread. :) *** calendarclass.prg *** FUNCTION dummy return define class zzz as CommandButton ..... enddefine define class xxx as Form ..... enddefine *** calendarclass.prg *** On Fri, Jun 19, 2015 at 9:29 PM, Dave Crozier <[email protected]> wrote: > Man-wai, > In fact if you make your > set procedure to .\calendarclass.prg > Then you project works -- .~. Might, Courage, Vision. SINCERITY! / v \ 64-bit Ubuntu 9.10 (Linux kernel 2.6.39.3) /( _ )\ http://sites.google.com/site/changmw ^ ^ May the Force and farces be with you! _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAGv=MJDpbovVyj8A8i8S-=cznk4tz88yyahfzdgjxyh0xby...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
