Scroll down for reply...

>>>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).
>
>Look - a good design has as few forms as possible, as few tables as possible, as few of everything as possible. Why do I need a ready made save button when my big A project only has two or three save buttons, total. You're just crowding the plate. Good design means less! Write your own navigtional processes, generalize, optimize - make it fast with your imagination.

Hi Terry,

It was just an example. I don't always buy into the Mies Van Der Rohe school of thought ("less is more"). Sometimes you actually need more. Using a framework for me so far has meant that I don't need to putz around with security issues, my app is already 3-tier and in the future, if I take it to client/server I will just have to make a few changes.

The framework I'm using, Mere Mortals, is very fine tuned towards optimal performance, so that's not really too much of an issue.

I think it's a matter of personal taste and choice, and believe me, if I had found it easier to accomplish all this on my own I wouldn't be using a framework, but if that were the case, at least I did look over the fence to see what's out there and didn't just decide that I don't need something I'm not completely sure about.

have fun!!!

Alex