Hi all vfp gurus,

We have a vfp app currently deployed that uses
a mscal-based calendar extensively (version 7).

The whole thing ran nicely surviving a
new generations of the ocx (8,9) by ms.

Enter office xp with a new ocx (version 10)
installed by a couple of our customers.

Now it looks like it does breaks "binary
compatibility".

That means that vfp forms with with a calendar
on it will break if you call some of their
properties (from msdn).

Looks like a new case of "dll nighmare".

Alternatives :

- rebuild the exe and installation routine
with the new version 10 ocx (until next bug),

- find a non-ms ocx with equivalent functionality

- instantiate the control dynamically instead
of painting it on the form.

Has anyone on UT used any of these solutions?

Any feedback is welcome.

Francois


Francois

We do not want all of our customers
to update their exe because one of
them