>I've had the same problem ("Property VALUE not found") with MSACAL70.OCX (included in setup) on one machine. I had the user run REGSVR32 'just in case', and that solved the problem.
>Should have thought that you'd get an error when the object was instantiated, if the class wasn't registered, so I don't know what exactly caused this...
>This has happened only on one machine, running a norwegian Windows 98.
>

It's likely that the control was there and registered, but a different version than the one you had him register, that didn't support the property that you were trying to access. With a little luck, the version you have will be a superset of the original one's functionality, and everything will continue to function; unfortunately, I've run into situations where I've placed different versions of a control on two different VFP forms (so far, only in different apps), and I now run into the problem of only being able to have one of them registered at a given time...

>Arne
>
>
>>I have an application running on a network drive in which some forms have ActiveX controls, primarily the oleCaledar. In the Init event of the form I initialize the oldCalendar with "ThisForm.oleCalendar.Value = DATE()". When the form is activated on my users PCs, the error "Property VALUE not found" is displayed.
>>
>>Does anyone know what I have done wrong here? On the development PC I have never seen the error and the setup routine includes COMCTL32.OCX to be placed in the windows system directory.