>>>I have built a multi-user application that has the ms activex
>>>calander in it. The problem is in the set up. The person who
>>>installs the program get it register on his system, but any other person how links to it gets either ole error, missing file or control not register. I have solved this problem by adding a INI file to my database. So each person installs it on their computer and changes the ini to locate the database on the network. This makes the code faster because it only access the database across the network. The only other solution is to check for the activate x control and if it is not there register it with the applicate. I'm not sure which way is better one might be a little fast but with less a user friendly solution. while the other would require less user setup.
>>>
>>>I was wondering if there is a better way or how do other
>>>people handle this problem?
>>>
>>>Charles
>>
>>
>>You don't have an error...it's working exactly like it is supposed to. How to handle this is to have
>>a system install that only installs the application and needed support files, no data.
>
>I know that is how it is suppost to work:) I was just wondering
>if there was a better way. It seems to me that VFP with Active-x
>or MS GRAPH don't make multiuser to user friendly.
>
>Charles



This really isn't a VFP problem. It's the way Windows is designed to work. These controls put entries
the registry so that ANY program that supports them can use them. Remember, VFP, Word, Excel, etc
all use the same graph program, so when you install MS Graph, it writes it's registry information so that
the other programs know how to launch it, where it is stored (folders on your drive), etc. The same
holds true for ActiveX controls.