Is it just me or are lots of people are relying too much on wizards and not considering the best design for the user interface? Access has great capability for interface design. I blame those bloody 'made simple' guides for not emphasising the importance of good design. Also many don't understand the abstract of databasing. A lot of people think a database record collection is like a spreadsheet table. Record collections don't in theory have to be in table form at all. The most important thing is how well data is stored and recalled. The problem with practical people (bless them) is they are totally stumped when what they fathom goes from what they can realise or visualise in front of them to something more abstract. As far as interface design goes these are my top pet hates.
That’s my rant over!
- Continuous forms
Why? One page one record simple. If your interface looks like a db table then it's pointless. Interfaces are supposed to make easy to enter, find and most importantly view that data. The only time I would consider using continuous form is on things like project time sheets but then again I think I would use an ActiveX control like a table (in the spreadsheet sense). With a dropdown for a the week # displaying the ‘table’ for that week with rows for projects and columns for the days of the week. Meaning one page equals one week of work. But in order to get an accurate week you need to ask them how many hours they spent on each project during the week and make it simple by allowing them to do it in one go rather than having to enter each project hours individually to the correct week and day. The code behind this however is not simple. Continious are reports fine. - Over use of subforms
Use subforms sparingly. If you are using subforms to save space on a fixed height form consider a different solution such tab controls. - Poor validation and crap data
Always validate data at the earliest and most stable point i.e on the table itself if at all possible. Controlling validation at interface level is much more difficult and is considered 'house keeping'. If you find yourself trying to code your way out of bad data then consider starting from scratch. - Poor control choice
Speaks for itself - Shit data entry
Make sure you make that critical distinction between data entry and data viewing if you don’t the lines will be blurred and most likely your user will look for the easiest way to enter data.
That’s my rant over!
Last edited:
)
I never heard Mike get angry why do you mention him? I am much more mardier than him. 
