CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 2 of 2
  1. #1
    Join Date
    Apr 2001
    Posts
    1

    Problem showing OCX on HTML page

    hi,
    I have the following OBTECT tag on a HTML page to show an OCX control. It just simply doesn't download and show on the client side. This seems to be happening in only a few of the clients, I have tried changing the IE security settings around but nothing happens.

    <object id="ucContainer1"
    classid="clsid:EA225710-22C7-11D5-A0DE-000102473C5A"
    codebase="prjContainer.ocx">
    <param name="_ExtentX" value="21273">
    <param name="_ExtentY" value="17806">
    </object>

    NOTE: This OCX has the "microsoft scripting run time" and the tab control referenced.

    In the same page I have the MScalendar control just to see if that downloads and shows, it seems to be working without a problem. The following is the calendar's OBJECT tag.

    <object id="Calendar1" style="LEFT: 0px; TOP: 0px"
    classid="clsid:8E27C92B-1264-101C-8A2F-040224009C02" VIEWASTEXT width="372" height="279"
    codebase="mscal.ocx">
    <param name="_Version" value="524288">
    <param ...
    ...
    ...
    <param name="ValueIsNull" value="0">
    </object>


    Any help would be greatly appreciated


    thanks,
    Shankar



  2. #2
    Join Date
    May 2001
    Location
    Birmingham, AL
    Posts
    2

    Re: Problem showing OCX on HTML page

    Please try setting the #version equal to -1,-1,-1,-1. Check the registry of your client machine to be sure there are no previous references to the OCX. Then hit the page from the client; by setting the version to this number, it should force the IDS to download every single time provided your codebase points to the location where the object can be found. I have always worked with codebase pointing to a CAB file instead of directly to an OCX, because my OCX always had dependency dlls it required in order to run.
    I had an issue one time where a certain imaging company had updated their control and their CAB file but the version number had not changed with the 'upgrade'. I was forced to write a script to strip all registry references to the old ocx and manually delete the files in order to correct the problem.
    Hope this helps.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  





Click Here to Expand Forum to Full Width

Featured