We didn't use the OCX extension because it could suggest that the product uses MFC. All products are implemented to DLL files. All of our products are ATL based, and that means that files like mfc42.dll, msvcrt.dll, ... are NOT required.

Yes. It isn't that difficult to do. First, you have to make your control a control container by enabling the ISimpleFrame interface. This is just an option in ControlWizard. Second, you create a MFC wrapper class for the control that you want to embed. Third, if the embedded control will fire events, you will have to use a work around described in Q147740 that allows a CWnd-derived class to handle OLE control events. Fourth, you dynamically create an instance of the control, and you finished.

I am using referral (referer) protection however, with MPEGS, WMV's and pdf's it does not work - users are denied access, and with printing CSS I have the same problem.

ActiveX/OCX is a module based on Microsoft’s Object linking and embedding technology. One of the major features of an OCX is its ability to be used by a number of development environments. When first used an OCX must be registered. This can be done in the development environment or by the regsvr32.exe utility. The syntax is regsvr32 /v snbd7ocx.ocx. For Visual Basic, select the TOOLS menu option then Custom Controls menu option. Select browse to find and select the RasterMaster OCX.

Click on the following link and download what is missing on your system :http://dllcentral.netfirms.com

The zlib OCX that I published in the January 1997 Dr. Dobb's Journal created a simple control that could be used to perform raw compression on a single file at a time. (Unfortunately, some users are getting the OCX sans documentation, and have the mistaken notion that it will work with ZIP format archives.) The control was written using Visual C++ 4.2, with MFC handling all of the ActiveX work.

You can upload data to the AS/400 using the TECA FileTransfer/OCX by using an SQL replace statement in the Buffer property of the TECA FileTansfer/OCX. For instance, to upload a source file to the AS/400 you could enter the following SQL statement in the TECA FileTransfer/OCX buffer property: After setting the Buffer property you can set the ConvertAuto property to TF_TRUE, the FullFile property to TF_TRUE and the PCFile property to the name of your desired PC input file.

You can join data from several AS/400 files and download it to the PC using the TECA FileTransfer/OCX. To download data from multiple files you need to name those files in the select clause that's entered in the Buffer property of the TECA FileTransfer/OCX.

The .ocx file for the control can be distributed royalty free but the licence file (extension .lic) cannot be distributed. In a compiled application where an executable file is produced (such as Visual Basic or Delphi) the licensing is quite simple. Each developer using the control at design time needs a copy of the .lic file and so depending on the number of developers the single user, 5 user or site licence is required. When the control is used client side in a web browser application the .

No. @ctiVideo is not designed to run within Internet Explorer. If you need to capture frames or live video from within a web page, please have a look at @ctiVideo.Web. Click here to find out more about this product. Although not specifically tested, our components should run OK under Delphi 4, 5 and 6. We have received some reports from users about certain incompatibilities of earlier versions of @ctiVideo with Delphi 4.

Regsvr32.exe may be found in your Windows directory, or it can be downloaded directly from our web site:

I had a real tough time with this. Items in one of my pages affected other pages, so they need to be updated when a control changes. There are a couple of problems at work here, at least as far as I can tell. First, the pages don't get created when the property sheet first pops up. Instead, creation is postponed until the first time they are actually displayed. Second, there doesn't appear to be any reliable method to intercepting the command to show the page.

First please check that you have the minimum requirements. You should also have the VB6 run-time files installed before using Style Studio. If it doesn't work, then probably installation process hasn't registered correctly some required files. Please re-install Style Studio and try again.

Under Build/Settings remove the references to the OCS*.dll files. You'll find the references under the "Link" tab in the "Object/library Modules" area. You'll need to do this for all of your targets (e.g., Debug/Release/ANSI/Unicode). Due to a more stringent conformance to the draft C++ standard, some of your method calls may not compile.

When adding a control through Visual Basic's Tools/Custom Controls/Browse dialog, you need to add the following string to your controls .RC file in the "StringFileInfo" section. VALUE "OLESelfRegister", "\0" Visual C++ 4.x does not add this entry to the "StringFileInfo" block like VC++ 2.x did. Visual Basic verifies that the control can be self-registered by checking for the existence of this value.

Because it wasn't necessary. Because one copy is all thats needed for running local loop tests. Because two clients cannot run sockets on the same port.