>>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...

You mean that if a control exists from before (in another version), the new version might just be copied to the system directory without actually being registered? Is this a known issue? If so, this would introduce another headache when distributing an application with activeX components...
The OCX-file in his machine after the installation was the same version and exactly the same size as the one distributed from the development machine. The users PC was brand new with not much more than windows '98, MS Office and Internet Explorer, as far as I know, so I think that there _probably_ wasn't an older version of MSACAL there from before.
This problem, although easy to remedy, makes me a bit worried...

Arne