To use classes in a PRG, you use SET PROCEDURE objVar = CreateObject(..)
OR objVar = NewObject(..) I have not found a way to subclass a PRG based class into a Class Library. How you separate your code/classes is a personal organization call. The more classlibs/prgs you have, the more things VFP needs to look through, or the more you rely on NewObject. The less you have, the more cluttered it feels. It's a balancing act. Tracy -----Original Message----- From: Joe Yoder Sent: Friday, January 09, 2009 5:09 PM My long term goal is to develop any number of classes to use in various projects in the same way I have used functions and procedures. My approach in FPD was to keep the general functions and procedures in a folder that was included on the path. This allowed me to access my udfs just like the Foxpro components and allowed me to eliminate needing to "set procedure". My first "define class" code is in a classes.prg file which needs to be named in a "set procedure" statement. Do all my coded classes need to be handled the same way or can coded classes be in individual files in a folder that is on the path just like I handled functions and procedures? When I advance to subclassing my coded classes - Can that code be included in the same folder or procedure file? I know that Visual classes can be stored in libraries. Can they also be stored separately in folders and located by placing the folder on the path? Is it advisable/possible to include a subclass of a subclass of a visual class in the same library? Apparently it is possible to subclass a visual class in code. Is it possible to subclass a coded class visually? Thanks in advance, Joe Yoder ternet.net _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/002101c972aa$922ab910$b6802b...@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.
