In order to use early binding you need a reference to the library which
contains the object you are trying to bind to.
Therefore in order to use early binding in this case you would have to use
the export the class and change the VB attribute method.
Although you refere to this as the "unsafe" methdo, this isn't really the
case it really should be described as the undocumented method. Just because
it's undocumented does not mean it's unsafe.
In summary; you can export the class, change the attribute and reimport the
class, you then have the choice of using early binding or late binding, with
early binding you will get intellisense halp.
Alternatively you can use a function to return an instance of your class, in
this case you are restricted to using late binding and therefore cannot use
intellisense.
--
Terry Kreft
MVP Microsoft Access
"Arno R" <arracomn_o_s_p_a_m@tiscali.nl> wrote in message
news:42285a7f$0$44084$5fc3050@dreader2.news.tiscal i.nl...[color=blue]
> Thanks, but if I do as you tell me Access protests: "Undefined Object"
> The class is in a codelibrary as I wrote.
> So I guess I just can't use Intellisense here ...
>
> Arno R
>
> "Stephen K. Young" <s k y @ stanleyassociates . com> schreef in bericht
> news:38q4tuF5ps8p0U1@individual.net...[color=green]
> > "Arno R" <arracomn_o_s_p_a_m@tiscali.nl> wrote in message
> > news:422764d1$0$44071$5fc3050@dreader2.news.tiscal i.nl...
> > ...[color=darkred]
> >> I reference the codelibrary and in a standard forms_module I use:
> >> Dim mc as Object
> >> Set mc=fclsMyClass
> >> 'Do stuff ...
> >> set mc = Nothing
> >> The code works, the properties are there BUT intellisense does NOT work[/color][/color][/color]
??[color=blue][color=green]
> >
> > For Intellisense to work, you might try declaring "mc" more specifically[/color][/color]
as:[color=blue][color=green]
> >
> > Dim mc as clsMyClass
> > Set mc=fclsMyClass
> >
> > - Steve
> >
> >[/color]
>
>[/color]
