Hey Christoff!

I don't know what the issue [really] is. The treeview,listview, toolbar, imagelists and progress bars are added as PRG classes and subclass from a VCX. The Slider is visually dropped onto the form (no VCX).

The project installs and runs on 95% of the systems. In certain instances, after it is installed, on some desktops - it pushes an error - in fact it pushes the error before the procedure file with the error handler is "loaded".

I have moved the error handler to the "top" PRG.

It works with the visual slider on most desktops. Just every once in a while, on some boxes - this error pops up when it runs - and tells me it can't find the error handling program.

So I don't know what it is. Should I turn off themes?

The project also creates a reference to CDO. I just assumed that CDO was part of the XP OS - so I did not test to assure the TYPE was an object. I have made that change, but not deployed. The project also creates a Word Object reference.

VFP 6 - using the Wizard - would install and run everytime - now - I hear from SA's at big shops tell me that most installs (not just VFP) require some time with "Regimon"!

What's that all about - should we now figure our some way to "automate" regimon so we can fix the install when the user first runs it?

But to your question - just one class - the "slider 6" is dropped on a form without a VCX.

I have 7 computers clean computers here. The installs are always good - just every once in a while - someone downloads a copy and tells me they have issues when it starts.

I don't know what it is. I just wonder why a MS tool project won't run on an MS XP operating system - almost like it's intentional - but - thank the maker - it's not just limited to VFP.

One SA in a shop where only one computer failed to run it told me there seems to be a resource conflict. IOW: VFP wants a system resource and the desktop does not want to give it up.

Thanks

>Hi Terry,
>
>>Did I read it wrong. Do visual OCX "drop-ons" also need to be encapsulated in a VCX?
>
>What ActiveX control is causing the problem for you?
>
>The reason for the need to add an ActiveX control to either a VCX or SCX lies in the licensing scheme. ActiveX controls can be created in two ways. Either they are loaded directly (which is what happens when you use them in a PRG) or from a OLE stream with property settings. That's what happens when you load an ActiveX control from a VCX/SCX. The OLE stream is the content of the OLE memo field.
>
>Most controls support two modes: Design mode and runtime mode. If you don't pass an OLE stream, licensed control start in design mode. In this mode they are looking for an installed license that allows you to use the control as a developer. Only if you installed the control, you should have such a license installed. If they can't find a license, you get an error message when you try to run the form. Usually that "License not found".
>
>When controls have been loaded with the proper license, the host can ask them to persist themselves into an OLE stream. This happens when you save a form or class in the Visual Designer in VFP. In this case the ActiveX control writes the license information into the OLE stream usually encrypted in some way. When you restore a control from the OLE stream, it uses the runtime mode. In runtime mode you cannot edit the control in the designer, but you can run it with the license information stored in the OLE stream.
>
>Hence, if the control relies on this licensing scheme, you either need a VCX file or the license information that tell the control to run in design mode, too.