 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
MS Access Forum / Modules / DAO / VBA / September 2005Compile Error - Procedure too big
I have a form which runs a process to check if any data has come back from a server. When there is data present, it runs a procedure. This procedure processes the data and then pauses for a set amount of time before checking again if there is data present. My problem? Well, depending on the data there are different types of routines that need to be run. Each line of code has a key that may run a different type of process. I need to rs.movenext each line of data as there is a header line, detail, and ending record line. I am getting a Compile Error - Procedure too big. Any solutions? Thank you VERY MUCH! Janis - STILL in Minnesota :) Hi, Janis. > I am getting a Compile > Error - Procedure too big. Any solutions? There are only two ways I know of to get this error: 1.) Too many lines of code; or 2.) Too many continuation lines for a single line of code within the procedure. If you have too many continuation lines for a line of code, then try to break this line of code into multiple executable statements. If you have too many lines of code, then look for repetitive sections of code that can be extracted from the current procedure and placed in another procedure and then called from the current procedure as many times as needed, perhaps with a SELECT CASE statement. HTH. Gunny See http://www.QBuilt.com for all your database needs. See http://www.Access.QBuilt.com for Microsoft Access tips. (Please remove ZERO_SPAM from my reply E-mail address so that a message will be forwarded to me.) - - - If my answer has helped you, please sign in and answer yes to the question "Did this post answer your question?" at the bottom of the message, which adds your question and the answers to the database of answers. Remember that questions answered the quickest are often from those who have a history of rewarding the contributors who have taken the time to answer questions correctly. > I have a form which runs a process to check if any data has come back from a > server. When there is data present, it runs a procedure. This procedure [quoted text clipped - 9 lines] > > Janis - STILL in Minnesota :) Thank you very much for responding!!! I ended up putting procedural calls in because, like you said, the one procedure was too long. Thank you for pointing in the right direction! Janis > Hi, Janis. > [quoted text clipped - 43 lines] > > > > Janis - STILL in Minnesota :) You're very welcome! Breaking up a large procedure into smaller logical pieces and putting each piece into a separate procedure will likely help make the code easier to maintain, too. Gunny See http://www.QBuilt.com for all your database needs. See http://www.Access.QBuilt.com for Microsoft Access tips. > Thank you very much for responding!!! I ended up putting procedural > calls [quoted text clipped - 62 lines] >> > >> > Janis - STILL in Minnesota :) |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.