Am Dienstag, den 23.05.2006, 15:08 -0400 schrieb Andrew Jensen: > Fourth – One size never actually fits all. Hearkening back to my my > comments regarding separating audiences by skill level I believe that no > single example will be appropriate nor adequate.
Something similar was my last thought before falling asleep yesterday: It could be a good approach to collect a list of features and techniques to show the user. If this list has matured the time will be reached to start working on creating examples. Building this list incorporates what you demanded: finding the best solution for the problem or at least tell the user there are other ways to his goal (if so). I'm not sure if the feature list should start at the point where the wizard macros leave off or if some very basic things are necessary to show, too. Some first things a database frontend creator stumbles upon: - having a foreign key and showing the associated value in a column (e.g. customers name for it's id) - setting a value of one foreign key column to a value contained in another table (showing the associated value as above), read as having a predefined set of values for a column - still the same task: input of a new value in a foreign key table when the predefined ones do not fit - showing a picture from a database in a form - input of 1:n data, well known "customer-orders" or "order-items" scheme I could list more, but what are other people thinking? The goal would be not to have self contained example applications but demonstrating the most used techniques. Regards, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
