Arthur Fuller
fuller.artful at gmail.com
Sun Jun 26 13:55:35 CDT 2011
I solved this problem, albeit in a rather idiotic way. I imported the form of interest from Time_And_Billing into my own app, stripped it of all Controls and RecordSources, changed the Title to "Enter your own Title here", and stripped almost all the code from the form. Now I load the template form + my previous form, Select All, Copy from the original, switch to the blank form, Paste. It's clumsy but it works. Speaking of which, it would appear that Access defaults the layout of both forms and reports to something called "Normal". To what does that term refer? Does it mean that should I create a form|report called Normal within a given database, all subsequent forms would emulate the same look and feel (i.e. header, detail and footer formats, generic buttons placed either on the Header or the Footer, all Header and Detail and Footer colors etc. copied, even a UsualSuspects set of default buttons or URLs, depending on your "Normal" preferences. Etc. Obviously, this would be so much simpler in a language that genuinely supported Inherticance, but my Client is not about to finance my education, sadly. I suppose that I'll end up porting the app to c# on my own nickel, as a learning experience. Not the greatest solution, but OTOH it's a real-world problem, and it beats a sharp punch in the eye. A. Even assuming this, my guess is that the concepts of "Normal" are app-specific "normal", whatever it is in the immediate case -- could be Single-Form with headers|footers like so, etc.s that their definitions apply to all apps rather than this specific app. IMO, a bad idea. I prefer a design model like this: a) within each app, there is an object called Normal_SR.frm 'Single Row b within each app, there is an object called Normal_DS.frm 'DataSheet c:within each app, there is an object called Normal_PV_frm 'acPivotTable ... etc. I wish there were a way (perhaps this is, and I don't know it) to The more significant problem is that I have apps in the field to which I would like to apply these design-principles. A related problem is that moving to A2K7-64-bit has cost me my most beloved MZTools. Now THAT is a DRAG, totally unanticipated and a significant headache since I have come to rely so heavily on MZTools. Oh well... I suppose that I could write its most useful components myself -- Yay! -- yet another non-paying gig. I'm beginning to think that it's time to return to my former career in tournament-backgammon. Back then, I had a sun-tan at least. Now all I have (to update Zappa's nomenclature) is a Monitor Tan. Charlotte, please expound on "Access Themes" and how to apply them etc. Thanks, A. On Sun, Jun 26, 2011 at 12:27 PM, Charlotte Foust <charlotte.foust at gmail.com > wrote: > It sounds like a theme, Arthur. I don't have 2007 on my machine any more, > so that's the best I can do. We used graduated themes in our VB.Net > applications. > > Charlotte Foust > >