Stuart McLachlan
stuart at lexacorp.com.pg
Sat Oct 18 06:28:24 CDT 2014
One that immediately comes to mind is maintaining multi-level hierarchies on a single form through cascading side-by-side continuous forms. I seem to do a lot of that. -- Stuart On 18 Oct 2014 at 5:20, Arthur Fuller wrote: > For a writing project I'm working on, I want to compile a list > (doesn't have to be precisely ten) of the most common tasks and > problems faced by Access developers. Perhaps I should explain my use > of these terms. First of all, I do not mean problems with Access > itself. > > In the first category I mean things like writing form_load and > form_open code; creating combo-boxes whose source is a named query or > Select statement; writing code to open a second form (for example, > when a double-click on one form automatically opens a second, related > form); that sort of thing. > > In the second category, I mean such things like creating master-detail > forms; creating forms that will enable the user to perform complex > queries (parsing the query form and assembling the SQL from the values > chosen by the user). I suppose that into this category might go the > need to write complex processing code that has little or nothing to do > with forms; writing custom UDFs that don't exist in Access, passing > values from one form to another; creating nested reports. > > I don't want to rely solely on my own experience in assembling this > list. So I'd like to reach out and take an informal poll here and see > what you think. > > -- > Arthur > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >