Jeff,

Something I have a problem with though, is that there are way too many threads here with titles such as "Access & Assign methods and their rightful standing in the OOP world". I used to attend the local FP user group fairly regularly until they the had a meeting on "Black Box programming". After they spent an entire hour discussing variable naming conventions, I started attending less and less. Too many programmer types do things cause they can, not cause it is of benefit to the user of the system.

PF

>There was a big thread here just the other day on UI. Stick around a few more days there will be another.
>
>Jeff
>
>
>>David,
>>
>>Thanks for the link to the "Hall of Shame". I've been looking for just the type of suggestions those folks provide. As a developer, I don't consider myself anywhere near the level of youself and others here. But I'm trying to get there. What I can provide now, is that I can sit down with users and translate their needs into a usable system.
>>
>>I think that the problem with way too many programmers is that discussions such as the one here on Access and Assign methods takes precendence over UI design.
>>
>>PF
>>
>>>Mike,
>>>
>>>Visit this site for a couple of view points. They also strongly argue against scrolling forms. http://www.iarchitect.com/shame.htm Also from my website on the links page is a link to Allen Cooper's website. He's the author of About Face, The Essentials of User Interface Design.
>>>
>>>If the form has boxed sections I'd be inclined to put each section on it's own page of a pageframe.
>>>
>>>>Let's assume that I'm creating software to complete a government form that is printed on a 14" sheet of paper. It seems that creating a "form" that looks as much like the official form is a good interface. I know there are issues with getting to parts of the "form" that are out of view. If you think that a scrollable "form" is a bad interface, how would you design the above example?