>I'm using the MS Calendar Control in my VFP 5.0a app - MSCAL.OCX. It says "MS Calendar Control 8.0" on the ActiveX controls toolbar when I add it to the form. On the properties sheet it says MS.Calendar.7.
>
>When I ship out my app to the user, using the SETUP wizard, I include MSCAL.OCX. On most of his machines, it works just fine (all Win NT 4.0, by the way). One ONE machine, when the calendar pops up, it is missing the month/year selector. I've had him manually copy a new version of MSCAL.OCX into the SYSTEM32 directory (and make sure there are no other MSCAL.OCX's floating around). Same problem.
>
>The other day, he installed NT on a new machine, and then installed my app - this machine also has the bad calendar control.
>
>Anyone know what might be going on? It LOOKS like I'm getting the wrong version of the calendar control. How does the system find these things? By the name? Or by some internal ID number? This is a real PITA, since I want to ship the app to a bunch of different sites, but the calendar control is a vital part of it, and I've got to figure out what is going and and fix it.
>
>Many thanks in advance for any insights you might have.
>
>Larry

The calendar control from VFP 5.0 was MSACAL70.OCX.
The calendar control from VFP 6.0 was MSCAL.OCX
They are mutually exclusive, meaning only one control can be registered at a time, even if both controls are on the machine.

Use REGSVR32 to register whichever one you need to have. REGSVR32 MSCAL.OCX. The MSCAL.OCX (version 8) works fine in VFP 5.0, BTW, you just need to use the .Object syntax to reference the .Value field, etc. (MyForm.Calendar.Object.Value)