|
-
Sep 24th, 2000, 03:33 PM
#1
Thread Starter
PowerPoster
Has anyone had this problem, and if so, do you know what causes it?:
Occasionally when editing code, the autolist members don't show up when you expect them to - for example, when typing a dot after an object, or the parameters of a sub or function don't display when you are coding a call to it (even though to the best of my knowledge all references are in place and the item is spelled correctly). This seems to be an intermittent problem.
Thanks for any insight you can provide.
"It's cold gin time again ..."
Check out my website here.
-
Sep 24th, 2000, 04:43 PM
#2
Addicted Member
Hi,
VB works pretty fine with this when objects are early-bound (ie. when you create a reference through Project>References), however, it doesn't work at all when you use late bound references (especially using CreateObject calls). Apart from that I can't think of any other examples that might stop it from working.
Hope this helps
Shaun
Web/Application Developer
VB6 Ent (SP5), Win 2000,SQL Server 2000
-
Sep 24th, 2000, 04:53 PM
#3
Monday Morning Lunatic
On my copy of VB5, it doesn't pop up the function definitions for Left and Right unless I use them as Strings.Left and Strings.Right.
I refuse to tie my hands behind my back and hear somebody say "Bend Over, Boy, Because You Have It Coming To You".
-- Linus Torvalds
-
Sep 24th, 2000, 07:04 PM
#4
Certain types of errors in code make the autolist thing stop working. Often the error can be in a completly unrelated class, usually its a bad declaration or something. Fix the errors, and the intellisense works again.
Every so often, I also have dramas with the string function (left, right etc.). Sometimes they don;t provide the autolist, other times they refuse to compile.
- gaffa
-
Sep 24th, 2000, 09:50 PM
#5
Thread Starter
PowerPoster
Thanks for the responses, folks. Further observation of the problem seems to point to what gaffa says, where certain errors in the code seem to stop it from working.
For example, I copied over the Form_Load and Form_Activate events from one form to another (which already had those events coded). With duplicate procedures in the same form, intellisense stopped working; once the extras were removed, it started working again.
The problem also occurred when I copied some data definitions that were declared with Private or Public from the general declarations sections to a Sub (naturally, variables can't be declared with those keywords in a Sub). Once these keywords were changed to Dim, the problem went away.
I know that this is not an earth-shattering problem, but just a minor annoyance. Thanks again for your input.
"It's cold gin time again ..."
Check out my website here.
-
Sep 24th, 2000, 11:18 PM
#6
Frenzied Member
I've also had it happen when the system is low on resources... go figure...
oOOo--oOOo
__ /\/\onte96
oOOo--oOOo
Senior Programmer/Analyst
MCP
[email protected]
[email protected]
Your results may vary.. some restrictions may apply.. pricing and participation may vary.. not available in all states.. professional driver closed course..quantities limited..
-
Sep 24th, 2000, 11:26 PM
#7
Member
M'Soft screwed that one up...
The Left and Right functions are buggy that way. They will never show the AutoList. It is a bug in VB5 and all the SP's, Microsoft never fixed it to my knowledge and they know about it (I've read the KB article, don't have it offhand though). I'm assuming that it works in VB6 ?
Glacius Cool
Concept Designer
VB5sp4,VC++6sp3
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|