One more thing...You really have to read the code to figure out some of the buttons. I use a highly standardized style of coding and designing so the functions will always work in my databases. Things like always naming sub reports with a "_sub" suffix, and using a "report" toolbar for all main reports.
Some of the functions like dev_TbrRemoveLookups() might break your databases if you use lookup fields in your tables. So always make a clean backup of your database before running any of those functions.
Regards,
Bill Mosca, Founder - MS_Access_Professionals
http://www.thatlldoit.com
Microsoft Office Access MVP
http://mvp.microsoft.com/en-us/mvp/Bill%20Mosca-35852
My nothing-to-do-with-Access blog
http://wrmosca.wordpress.com
---In MS_Access_Professionals@yahoogroups.com, <JohnV@msn.com> wrote :
Giorgio-
Maybe Bill (the author) can jump in and explain. If you were using 2003 or earlier, you could edit the toolbar to see what it does. In 2007 and later, you'll have to navigate the CommandBars collection in code to try to figure it out.
John Viescas, Author
Microsoft Access 2010 Inside Out
Microsoft Access 2007 Inside Out
Microsoft Access 2003 Inside Out
Building Microsoft Access Applications
SQL Queries for Mere Mortals
(Paris, France)
On May 26, 2015, at 12:06 PM, giorgio_rovelli <no_reply@yahoogroups.com> wrote:If you check out this DevToolBar.jpg you'll see the first button on the left of the Dev Toolbar is titled IndexMod but when I press it nothing happens. I've imported the supporting BasDevToolbar module but how does one know which part of the code is run when you press this button? I don't see any reference to IndexMod in the imported code.
__._,_.___
Posted by: wrmosca@comcast.net
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (17) |
.
__,_._,___
Tidak ada komentar:
Posting Komentar