My MS Access Blog
Tips, tricks, best practices and more about Microsoft Office Access and Visual Basic for Applications (VBA). Links to great articles and posts around the web plus some things I've learned that I'd like to share.
Programming The VBA Editor describes methods for programmatically interacting with the VBE editor. Quote:"You can use these features to write custom procedures that create, change, or delete VBA modules and code procedures." The article is written for Excel but I think it should be adaptable to Access. (I haven't tried it yet- if you try it let me know how it works!)
at
6:00 AM | Permalink
|
Tweet this!
| Add This!
| Blog This |
UtterAccess is the web's leading help forum for Microsoft Access. The community of Access enthusiaists who post there provide help to newbies and veterans alike, always in a friendly and supportive manner.
Access 2003 resource Centre on MSDN
Access Developer Portal on MSDN
Allen Browne's tips for Microsoft Access Allen Browne is one of the web's leading authorities on Access. Several of his articles are the standard reference for the topic at hand. Allen is also the most often cited cataloguer of Access bugs and the related work-arounds.
The Access Web This site, established way back in '98, features tips and solutions from several Access MVPs. The code samples posted here are always clean and effective. Often you won't find a lot of text, but you will find code that works. The solutions here are cited all over the web as the best way to get things done.
Stephen Lebans' site is the authority on the web for some types of solutions. It's a site every Access developer should know. You'll find tips, plus downloadable working solutions ranging from zooming images in and out, to disabling the mouse scroll wheel, to a calendar, to creating PDF files. In particular I look to Stephen's site first for advanced topics related to forms and reports, especially interacting with the Windows API.
2 comments:
Thanks for posting this! The guidance is close, but still needs tweaking for Access. For example, they have a few variants that they say will work, such as:
Set VBAEditor = Application.VBE
But for Access, you need to use:
Set VBProj = Application.VBE.ActiveVBProject
But once you adjust to the slight differences between the Excel and Access models, it's a good place to start.
Take a look at this job posting -
https://jobs-hersheys.icims.com/jobs/4833/job
Post a Comment