Visual Basic Errors

S

smokey1111

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?
 
S

smokey1111

It does not say a code it just says:

Complie error:
Method or data member not found
 
D

Duane Hookom

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?
 
G

George Nicholson

Duane:

What? You mean you haven't heard about the infamous "Ln74" error?

:)
 
D

Duane Hookom

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...
 
G

George Nicholson

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...
 
K

Klatuu

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.
 
T

Tim Ferguson

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
 
Top