> > >Hi, > > > >Could someone please clear my doubt about FrameWorks. > >I am hearing lot of Frameworks here. What exactly is a Framework? > > > >I have created many class libs which manages File Maintenance, > >One-To-Many Forms, Report Forms, Custom Controls, Utilities etc. > > > >Can this be called a FrameWork? > > > >TIA, > >Biju > > Biju, it sounds as if you have made a good start at your own framework. > The purchased frameworks give you libraries that handle logons, user > security and form management at the macro (# of copies of forms open, form > name in Windows menu) or micro (user security for each field) as well a > sample controls that are linked through form properties for easier data > handling (a list that defaults to an array-type list property for its > source if the recordsource is empty) etc. > > Once you have learned what one of these frameworks can do (the first > application you do will leave you with either ulcers or a LOT less hair) > the succeeding apps become much easier than your original stand-alone > libraries. > > An added advantage is you tend to develop a common look & feel in your apps > which your users often feel more comfortable with. > > HTH > Barbara Thanks a lot, Barbara. Now its clear. I think I have most of those features in my frame work. I may need to enhance it. Can I ask a few more clarifications? By using 'Frame Works', I think we have to learn VFP as well as a FrameWork? Right? What about maintenance? Will it be like telling 'Sorry, VFP doesn't support that' or 'FrameWork doesn't support that!'? Since we are developers and already using a visual tool, isn't better to stick to our own code? More over u can put your imaginations there and learn at the same time! For eg. I really enjoyed making objects (I see them as human beings) like StoreKeeper, PersonnelManager, SystemAdminstrator etc. It was great fun! But if its gonna lose my hair, well, I'll think about Visual MaxFrame :^) Regards, Biju