XP/2000 Compliance

[Tom Sipos]

I have an application that began life as a 16bit VB3
application based upon the Jet 2 engine. It is currently
in VB6 on the Jet 3 engine but retains many of the VB3
contructs (eg. dynasets, DAO data controls).

A customer has requested that my application be brought up
to XP/2000 standards. Is there a white paper available
which lists those components which are no longer
officially supported by MIcrosoft in XP and 2000. I need
it right down to the DLL/OCX version number.

[Joseph Conway \(MSFT\)]

You may be able to find information on that on the MSDN website.

"Tom Sipos" > wrote in message
...
> I have an application that began life as a 16bit VB3
> application based upon the Jet 2 engine. It is currently
> in VB6 on the Jet 3 engine but retains many of the VB3
> contructs (eg. dynasets, DAO data controls).
>
> A customer has requested that my application be brought up
> to XP/2000 standards. Is there a white paper available
> which lists those components which are no longer
> officially supported by MIcrosoft in XP and 2000. I need
> it right down to the DLL/OCX version number.

[Joseph Conway \(MSFT\)]

You may be able to find information on that on the MSDN website.

"Tom Sipos" > wrote in message
...
> I have an application that began life as a 16bit VB3
> application based upon the Jet 2 engine. It is currently
> in VB6 on the Jet 3 engine but retains many of the VB3
> contructs (eg. dynasets, DAO data controls).
>
> A customer has requested that my application be brought up
> to XP/2000 standards. Is there a white paper available
> which lists those components which are no longer
> officially supported by MIcrosoft in XP and 2000. I need
> it right down to the DLL/OCX version number.