Its clear to the developer how it works, and a computer savvy person can figure it out on their own pretty quickly, but the computer illiterate presents a huge obstacle. Oh Really! ).Ĭontinuing the issue of the user and interface issues. My bet is he will have hit on various snags within fifteen minutes after starting (I should know. PS I found that a good way of testing your solution for robustness is giving it to test to your least computer savvy user. Filemaker is very open in this respect, and a power user will not normally have trouble recognizing what and how, but as soon as you develop for others, it starts to pay off to start closing all the various entry points of filemaker's many functions - and start developing for specific procedures, so only one mode of finding a record (by your procedure), one mode of creating a new record (by your procedure), one mode of creating a monthly report (you get the drift).smiley_cool That is why solutions should be built so, that at any one time it is clear to users what the context of a screen is - browse or find. the difference is quite subtle to the casual observer. a possible cause of records seemingly not being saved is that the user thinks he is in browse mode, while in fact he is in find mode. Record saving should be automatic unless the option is unchecked, and then a warning message should appear.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |