Sorry, can't be done.
Anybody who HAS used VB can come up with 10 questions that one can only learn from actually using the product.
This is true for most any product, not just VB.
For example, if you've actually used a compiler, you should be able to answer these questions:
What's the most common, or annoying, or misleading error mesasge you've ever gotten?
Every compiler has at least one of these that wil stick in your mind.
How do you set a breakpoint, view a variable while debugging?
What directory has to be in the search path? The library search path?
How do you enter debug mode, or exit it?
Which version of the compiler do you use? Name two things that got better
and two things that got worse during the last compiler upgrade.
Name three run-time errors, and what you do to fix them.
Can you write a DLL with this language? What's the compiler option?
What can't you do with this language?
Name five more things that are wonderful or annoying about the language, the IDE, or the libraries.
--------
Thee answers cannot usually be found in the manual, it's what separates the manual-glancers from the real experienced users.
Regards,
grg99
Main Topics
Browse All Topics
by: corduroy9Posted on 2003-09-11 at 05:33:22ID: 9336293
English grammar and communication skills in your written and spoken word do count...which isn't reflected very well in your question.
For VB specifically, you should be able to speak comfortably on the following subjects:
standard programming concepts (loops, variables, event-driven programming, etc.)
error handling
object properties
different object types
project components & dependencies
the different files used in a VB project
the different products you can produce with VB (EXEs, DLLs, OCXs, etc.)
...just to name a few