ActiveX c1Query8.ocx doesn't work on framework 4.5.2 with x64

ActiveX c1Query8.ocx doesn't work on framework 4.5.2 with x64

Posted by: kur.an87 on 11 September 2017, 11:32 pm EST

• 

  kur.an87

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 11 September 2017, 11:32 pm EST

  Hello, We met a problem with x64 verison on framework 4.5.2. Take a look at screenshot in attachment. If I switch project to x86 version and use x86 version of ocx - everything works. Could you please give me some solution or maybe simple example project vs2015 which works on x64?

  I have tried a lot variants, but always when c1query added as control and have linked c1queryframe, application crashes with “Attempted to read or write protected memory”. Ocx file info in the second attachment.

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 13 September 2017, 8:58 pm EST

  Hi,

  Your query has been answered in SupportOne case 285712 you created. Please continue the thread over there in order to avoid any confusion.

  Thanks,
  
  Pragati

• 

  kur.an87

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 7:15 pm EST

  Some error appears when add attachments

• 

  kur.an87

  • Post Options:
  • Link
    Copy

  Posted 26 September 2017, 2:28 am EST

  Hello,

  As of now there is no solution and this task is under investigation of component one developers for 2 weeks already

  Can we get some estimation or advice how to make it works on win10 x64 with 4.5.2 framerowk ?

• 

  elena.dovbenko

  • Post Options:
  • Link
    Copy

  Posted 26 September 2017, 3:05 am EST

  Hi Pragati

  This case is very important for us, because we cannot release new version of our app with broken query control.
  
  Could you please keep this problem and solution public, so management team can track progress

  Thank you

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 26 September 2017, 6:27 pm EST

  Hi,

  I understand that. This case is with the developers on high priority. Will update the thread once there is anything from them.

  Note: Our ActiveX controls are in maintenance mode.

  Thanks,
  
  Pragati

• 

  elena.dovbenko

  • Post Options:
  • Link
    Copy

  Posted 27 September 2017, 3:46 am EST

  Hi Pragati

  Could you please mark this thread as not answered and post solution here as well

  Thank you

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 27 September 2017, 6:13 pm EST

  Hi,

  I am sorry but this is not possible to mark this post as unanswered at the moment. Our website is undergoing changes and this is in to-do list.

  Will definitely post the update here as it comes.

  Thanks.

• 

  elena.dovbenko

  • Post Options:
  • Link
    Copy

  Posted 3 October 2017, 5:39 am EST

  Hi Pragati

  Is there any news from development team? were they able to reproduce this bug?

  Thank you

• 

  grapecity

  • Post Options:
  • Link
    Copy

  Posted 4 October 2017, 7:42 pm EST

  Hi,

  There have been no response from the Development Team yet.
  
  Hence I have asked for an ETA on this case and have once again raised concern on this issue.
  
  Also, the issue is currently marked with top-most priority in the To-Do list.

  I would update you as soon as we receive any updates from them.

  ~Ruchir Agarwal

• 

  edovbenko

  • Post Options:
  • Link
    Copy

  Posted 16 October 2017, 6:17 am EST

  Hi Ruchir Agarwal

  Are there any news about this problem? Were development team able to reproduce this?
  
  Is there any ETA?

  Thank you

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 24 October 2017, 10:33 pm EST

  Hi,

  We have tried verifying the behavior on a Windows 7 64 bit machine at our end. The 64 bit version runs correctly on a Windows 7 machine. However, to make the 64 bit to work on Win7, it was necessary to configure explicit 32 bit (x86) and 64 bit (x64) builds in the sample. AnyCPU is inappropriate for all our controls because they are native code and not .NET. If the program process starts as 32 bit and an attempt to load a 64 bit OCX is made, the program will crash. Similarly, the opposite is also true.

  But on a Windows 10 machine, there seems to be some problems. The developers are looking into it but there is no ETA as of now. It will take time in fixing.

  Note: Our ActiveX controls are in maintenance mode.

  Thanks,
  
  Pragati

• 

  elena.dovbenko

  • Post Options:
  • Link
    Copy

  Posted 14 November 2017, 4:43 am EST

  Hi Pragati

  This problem is still very important for our clients, because we need to allow them work with x64 application
  
  What is ETA for resolution of this problem?

  Thank you

• 

  Pragati.Kaushik

  

  • Post Options:
  • Link
    Copy

  Posted 19 November 2017, 10:08 pm EST

  Hi,

  While the developers are still working on this case, they have shared an update on this.
  
  The 64 bit version of the program is working correctly for them on a Windows7 machine but not on a Windows10 machine. When trapping all of the exceptions, it appears that the exception thrown that stops the program from running is associated with IConnectionPointContainer of the System.Windows.Forms. The generated interop code by Visual Studio does not appear to be addressing the objects correctly with .NET.
  
  Though, as of now they could not find a solution or workaround to this issue but they are still working on this case. This might take a few days for them to find out a resolution to this.

  We will keep you updated with the information we receive from development team.

  Thank you for cooperation.