[AccessD] A2k3 Object Browser

<<<
Apparently they actually do change it and it breaks things.
>>>
John,

I have not seen it changed for 5+ years I have been using it.
"COM is dead" now - in the sense it will not be getting extended - so my
guess tlbinf32.dll will never change

> OLEPrint by Starprint.
It's written on VB6 so my guess it uses tlbinf32.dll

> I am back to square one on doing this myself since everything
What is you task?

Shamil

----- Original Message ----- 
From: "John Bartow" <john at winhaven.net>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Tuesday, November 08, 2005 5:50 AM
Subject: Re: [AccessD] A2k3 Object Browser


> Thanks all for your suggestions.
>
> I am back to square one on doing this myself since everything I have
> investigated comes up short. The problem may be that many of them rely on
> tlbinf32 which MS says is unsupported, undocumented and can "change
without
> notice". Apparently they actually do change it and it breaks things.
>
> I found one program that seems to pull the info up nicely for reports,
> OLEPrint by Starprint. Other than that th eother programs and scripts
either
> gave incorrect info or didn't run?
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com