Bill Benson
bensonforums at gmail.com
Sat Oct 18 07:25:02 CDT 2014
An increasingly needful but unhappy task is finding a way to make use of older databases with good integrity under the configuration they had in Ac2003, and making them openable, less so working, in Ac2013. Another task is forcing the columnwidth of list box and combo box columns to match the contents they are required to display. Sometimes in Access it is easier to just plus or minus it, because the controls I use on an excel user for do not behave in a manner conducive to this excercise, in MS Access. Another often neglected task whichbshould be done always, is to insure updates for permanent entity and transaction tables get logging, at a minimum updates to the LastUpdatedBy and LastUpdated fields. Another task us deciding how much data to keep in history versus current transaction tables, and of course splitting front and back ends, which you might have already covered. Putting relationships on is a good thing to do as its own task, and what I like to do afterwards is bring the database into Visio2010 (last release that had this feature) using reverse engineer function, to see that things are set up as I expect they are, I find this helpful in labeling of PK and FK elements. I do this mostly after adding the most important fields to tables (not all characteristics) just to check all my Not Nulls, keys, arrow directions. Not everyone works in this dual design environment, but I find it helps me to have 2 perspectives and visio is a nice db documenting interface. Another task is making use of all the column width and hiding and ordering potential within data sheet form columns / controls, and having devices that let application remember user preferences. That goes for a lot of things - remembering user preferences. On Oct 18, 2014 7:37 AM, "Arthur Fuller" <fuller.artful at gmail.com> wrote: > Thanks, Stuart. Come to think of it, I do a lot of that too. I'll add it to > my list. > > A. > > On Sat, Oct 18, 2014 at 7:28 AM, Stuart McLachlan <stuart at lexacorp.com.pg> > wrote: > > > 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 > > > > > > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > > > -- > Arthur > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >