 |
 | 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 2005Visual Basic Errors
I'm working with a database for a tabulation programs. I'm using a scanner pen to ender barcoded numbers into the program and every time I scan someting into the screen Visual basic comes up with an error and when I try to debug and compile the same error comes up. Does anyone have any help? What's the error & what's the code where it occurs?  SignatureGeorge Nicholson Remove 'Junk' from return address. > I'm working with a database for a tabulation programs. I'm using a scanner > pen to ender barcoded numbers into the program and every time I scan > someting > into the screen Visual basic comes up with an error and when I try to > debug > and compile the same error comes up. Does anyone have any help? Complie error: Method or data member not found > What's the error & what's the code where it occurs? > [quoted text clipped - 4 lines] > > debug > > and compile the same error comes up. Does anyone have any help? And what's the code that's generating that error? SignatureDoug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) > Complie error: > Method or data member not found [quoted text clipped - 8 lines] >> > debug >> > and compile the same error comes up. Does anyone have any help? It does not say a code it just says: Complie error: Method or data member not found > And what's the code that's generating that error? > [quoted text clipped - 10 lines] > >> > debug > >> > and compile the same error comes up. Does anyone have any help? It looks like when I go to debug and compile it stops at Ln74, Col 25 > I'm working with a database for a tabulation programs. I'm using a scanner > pen to ender barcoded numbers into the program and every time I scan someting > into the screen Visual basic comes up with an error and when I try to debug > and compile the same error comes up. Does anyone have any help? I kinda doubt Doug Steele (or anyone else) can see the code at Ln74, Col 25. Do you think you could copy this line with significant lines before and after it to paste into a reply? SignatureDuane Hookom MS Access MVP > It looks like when I go to debug and compile it stops at Ln74, Col 25 > [quoted text clipped - 5 lines] >> debug >> and compile the same error comes up. Does anyone have any help? Duane: What? You mean you haven't heard about the infamous "Ln74" error? :-) SignatureGeorge Nicholson Remove 'Junk' from return address. >I kinda doubt Doug Steele (or anyone else) can see the code at Ln74, Col >25. Do you think you could copy this line with significant lines before and [quoted text clipped - 9 lines] >>> debug >>> and compile the same error comes up. Does anyone have any help? Yes, I have heard of "Ln74" but not the "Col 25" variant... It does raise a question regarding the programming environment since most error messages in VBA won't provide the line and column numbers like some other applications. You would need to do a fair amount of investigation to find the specific line number and column number. All of that investigative talent suggests it wouldn't be too difficult to copy and paste the lines of code around the erroring line in a reply. Either that or we are not talking about Access VBA... SignatureDuane Hookom MS Access MVP -- > Duane: > [quoted text clipped - 15 lines] >>>> debug >>>> and compile the same error comes up. Does anyone have any help? >You would need to do a fair amount of investigation to find the specific >line number and column number. Actually, that info is displayed (with exactly that syntax) on my VBE Standard toolbar (both Office XP & 2003), so it's not a huge problem to provide it. Helpful to make sure looooong sections of code indentations start & end with the same column#. However, "Col 25" indicates that the info box was specifying the cursor's current position, not necessarily the current line of code. My experience is that "Col 1" is always specified when a break in running code is initially encountered and the current line is highlighted (The cursor isn't "anywhere" until you click in the code pane). Once you do "click in", the info refers to the cursor position, which may have nothing to do with the highlighted line. So who knows... SignatureGeorge Nicholson Remove 'Junk' from return address. > Yes, I have heard of "Ln74" but not the "Col 25" variant... > [quoted text clipped - 26 lines] >>>>> debug >>>>> and compile the same error comes up. Does anyone have any help? LINE NUMBERS!!! Wow I haven't worked with line numbers since 1986. I really miss them. It is really hard to write good spagetti code without them. > >You would need to do a fair amount of investigation to find the specific > >line number and column number. [quoted text clipped - 42 lines] > >>>>> debug > >>>>> and compile the same error comes up. Does anyone have any help? > Wow I haven't worked with line numbers since 1986. > I really miss them. It is really hard to write good spagetti code > without them. <homer>MMMmmmm spaghetti code </homer > Tim F |
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.