>>>>Very roughly speaking, it's like a skeleton upon which you build your application. It usually comes with pre-built classes, forms, etc with a lot of functionality to address issues like security, forms management, data access, etc., which means that in most cases you won't have to reinvent the wheel.
>>>
>>>What do you mean when you say: 'You won't have to reinvent the wheel'?
>>
>>You don't have to create a number of classes from scratch. It saves you time.
>
>So, you're saying that the 20 seconds it takes to drop a command button on a form, change its caption to "Save", and then point to a method specific to the file structures my app is using could be reduced to 10 seconds?
Actually, sometimes the "Save" button is ALREADY waiting for you on the form along with "Cancel" and, depending, on the framework, some other buttons or even a navigation toolbar.
If you haven't used a framework, you owe it to yourself to at least LOOK at one and then see if it's something you could benefit from (not all frameworks are suited for all people and not all people are comfortable using a framework).
Alex
Low-carb diet not working? Try the Low-food diet instead!