Access Database Homepage

Type keyword or phrase to search:

 

 

 


Access Database Homepage

The know how and power behind access database

Want to teach yourself Access? Free online guide at About Access Databases
 
Access Database Introduction
A database is a collection of information. an access database provides a mechanism for storing, retrieving and manipulating that information. access databases.com click here to get free access da...

How find the errors in access database vba programing, which was already done?

Question: How find the errors in access database vba programing, which was already done?

(Posted by: Raj on 2010-06-01 10:06:34)

I am MIS Lead, i am using the database to download the reports and which is created by another team. On daily basis i am getting changes in the data base i could i view the errors from VBA coding or the changes?


Answers:

Posted by: Ben on 2010-06-04, 23:55:57

How find the errors in access database VAb programing, which was already done? Firstly, so the we are clear, VBA can not see any data in your database it is a procedural language for manipulating objects within Access (or any other application). If you are referring to new reports being added which have VBA code attached and your are getting errors when running a report then you will need to debug them and step through the code to see which line(s) of code are causing offence. Proviiding you have access to the code, load the VBE (editor) by first being in the design view for a report (or any object). Press SHIFT + F11 to load the VBE window. Locate the procedure like when the report is opened or loaded and add a breakpoint on the first or line of code you wish to pause the procedure when running it again. Press the F9 function key where the insertion point is placed on the line of code (turns this line purple). Now run the procedure (F5 function key) and then when the procedure is paused on the breakpoint use the F8 function key to step one line at a trime into your executed code line and see what and where the error is really happening. To help with the debugging process you may want to use the Watch View and an Immediate Window view (CTRL + G) and use the '?' followed by a space and then the command you wish to test to view current values as a temporary output. Take the time to look up help on the VBE debugging tools to understand my comments further but I can not help you analyse the code without have access to your code! Hope this helped Ben Beitler

  

Powered by Yahoo! Answers (R)


Back to Previous page

Google News will be listed here
Go Articles will be listed here

Bookmark Access Database Homepage


Want to teach yourself Access? Free online guide at About Access Databases

 

 
Sitemap | Terms of Use | Privacy Policy | Contact

© copyright 2010 Access Database.com, All Rights Reserved.

Legal Notice: This website is powered by Amazon®, Adsense, Clickbank®, Yahoo!® Answers and Youtube. All trademarks are copyrighted by their respective owners. Please read our terms of use and privacy policy.