intellisense feature not appearing 1

[Vie]

Hi,

I'm writing a piece of code that uses ADO but I can't get the intellisense menus to appear when I hit "." and such, as in:

Set col2 = New ADOX.Column
col2.Name = "Floor"
col2.Type = adInteger
col2.DefinedSize = 30

.Name, .Type, .DefinedSize and also the enum adInteger should all appear in intellisense lists but they don't.

I have the references checked for:

Microsoft ActiveX Data Objects 2.5 library
Microsoft ADO EXt. 2.5 for DDL and Security

Can anyone help me to get the intellisense feature to work?

Thanks,
Vie

 

[PHV]

Instead of this:
Set col2 = New ADOX.Column
try this:
Dim col2 As New ADOX.Column

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[Vie]

Thanks PH, That does the job! But according to Access Developer's Handbook collapsing Dim and Set statements into one line slows down the code. Do you have any ideas why the intellisense isn't working?

In any case, thanks very much!!!

 

[PHV]

Just because col2 was not dimmed as an ADOX.Column object.
The intellisense engine don't try to interpret the Set statements in design time.

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[Vie]

Actually, it was dimmed at the beginning of the sub and then set later.


Dim col1 As ADOX.Column

Set col1 = New ADOX.Column


I have a sample database with almost the same code in it and the exact same references checked and in that database it works. In my database, it doesn't. Can't figure it???

 

[PHV]

col2 too ?

Hope This Help, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884

 

[Vie]

Yup. Any ideas why?

 

[Vie]

Putting this one to rest in case anyone else has this problem and reads this thread. How I worked it out: I copied a sub from another database where intellisense works into my database and ran the code. Now intellisense works in my database too.

It's still a mystery to me why this happened or why this fix fixed it, but there it is.