Gustav Brock
Gustav at cactus.dk
Sat Dec 7 04:19:35 CST 2013
Hi Charlotte OK, I can see you have taken your precautions, and when the average user is kept away, it should be doable. And after all, Access is an end-user product! /gustav >>> charlotte.foust at gmail.com 06-12-13 22:41 >>> Gustav, It may turn into a monster, but admin maintenance is the entire basis for the contract. I've managed to get my arms around most of the peculiarities and wrote some code to make sure the nav forms and buttons are a consistent color no matter what office theme they're designed under. They're not going to be writing a bunch of code, but they will want to add tabs to the nav forms. Not everyone, mind you, just a handful of engineers who will have as extensive a knowledge transfer as possible before I walk out the door. As for ribbons, they would be even more difficult for non-developers to maintain and modify. This project is designed from the start to have a limited number of super users tweaking it on an ongoing basis. My job is to use tools that they can easily (well, relatively easy anyhow) extend. This is not my baby, I'm just its surrogate mom. Charlotte On Fri, Dec 6, 2013 at 3:22 AM, Gustav Brock <gustav at cactus.dk> wrote: > Hi Anita > > Maybe I've seen too much! > > The difference could be, that users in general believe they can handle Excel > while it is opposite for Access. So maybe a user maintained Access > application will receive a little more respect than an Excel workbook. > > /gustav > > > -----Oprindelig meddelelse----- > Fra: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] På vegne af Anita Smith > Sendt: 6. december 2013 09:56 > Til: Access Developers discussion and problem solving > Emne: Re: [AccessD] Access 2010 + Navigation Forms > > Oh but Gustav, you are so upbeat It's hard for me to curb my enthusiasm ;-) > > > " After some years it will end as an advanced Excel workbook where no one in > the end knows why and how, nor by who it was created, and everything is a > mess." > > > > Anita Smith > > > Hi Charlotte > > At the contract I am working on we gave up on the Navigation form for > reasons though not identical then similar, and decided to bite the bullet > and use the ribbon. It allows you to move many of the buttons you otherwise > have sitting here and there for various tasks to a well-known location with > strict design and behaviour. > > > /gustav > > -----Oprindelig meddelelse----- > Fra: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] På vegne af Charlotte Foust > Sendt: 5. december 2013 22:06 > Til: Access Developers discussion and problem solving > Emne: [AccessD] Access 2010 + Navigation Forms > > Have any of you guys played with these? The contract I'm on requires that > the product be maintainable by non-developers, engineers who have been to > Access classes but aren't fluent in it and don't tweak it on a daily basis. > In the past I usually used tab controls and a fairly large amount of code > to design the user interface, but that isn't an approach that they would be > able to sustain. One problem with Navigation Controls in Access is that > there is a wizard that builds a Navigation Form but I don't see any way to > use the controls on another form, and the wizard totally ignores Normal form > settings and even the Windows Themes setting in options. I built code to > set the colors on the Open event of the Navigation Form but you have to use > RGB values to set them, and I don't see an easy way to make that modifiable > for when I'm gone. > > Any suggestions? One thing I learned accidentally is that if you set the > display size to 125%, you see some odd effects in the navigation control and > nav buttons. Those disappear when you fall back to 100%, so apparently the > control is for people with normal eyesight! > > Charlotte