If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
Access 2007 Ribbons
Thanks Albert,
I have come up with something that I will try for a while. I define all of my ribbons, including custom tabs, with startFromScratch="true" and load them via my 'appstart' code. The code will check for a specific command line argument. If the command line argument is present, I replace startFromScratch="true" with "startFromScratch="false". That way, during development, I have full ribbons as well as the custom tabs that the users will see. I have been using that method for setting many of the database and application options for some time, but the ribbon throws a slightly different curve. I typically use shortcuts to open my apps anyway due to the many versions of Access I work in, so I can just include the command line there. Then, when ready to test in user mode, I start the app without the shortcut. -- AG Email: discussATadhdataDOTcom "Albert D. Kallal" wrote in message ... That way I could have full ribbon functionality for development purposes (and certain power users) and only my custom tabs for normal users. You just have to use the shift key during startup... Of course, during development, you will hold down the shift key so your startup settings don't run. You then develop for awhile, and then to test in "user" mode, you exit..and then re-enter the application without the shift key bypassed. You will likely do this dance all day long as you run/test as user mode, and then flip back in to developer mode (shift key used..so you don't get the main custom menu). So, you can't develop, or really modify things when you run your application with the startup settings...so you must shift-by-pass them when you want to work. And, in fact, I use alt-f4 to exit the application...the accdb file should still be highlighted in the windows explore..so, then you hit enter key (and, hold down shift key if you need be). This key stroke sequence and exiting and re-entering the application will occur CONSTANTLY all day long when you are developing. When you finally have things just right...you create the accDE you plan to distribute... |
|
Thread Tools | |
Display Modes | |
|
|