试图调用OLEDB提供使用VB6窗体应用程序时消失窗体、应用程序、OLEDB

2023-09-06 05:39:59 作者:时间秒杀一切

我必须从WinForms应用程序我的水晶报表使用OLEDB提供程序(用于Sung盯Investran)。使用.NET 4,水晶报表VS2010。 OLEDB提供程序有一个参数对话框,我相信这是开发在VB6。当我把这个OLEDB提供程序与查询不带任何参数,它工作正常。但是,调用任何查询与参数的时候,整个应用程序只是消失。一切工作正常的Windows XP,但有这个问题,在Windows 7的应用程序被编译为仅适用于x86平台。尝试与全平台也同样的问题。 我看到在Windows事件日志两个错误

I have to use an OLEDB provider (for Sungard Investran) from my crystal reports in Winforms Application. Using .Net 4, Crystal Reports for VS2010. The OLEDB Provider has a Parameters Dialog, which I believe is developed in VB6. When I call this OLEDB provider with Queries without any Parameters, it works fine. But when calling any Query with Parameters, the entire application just vanishes. Everything Works fine on Windows XP but has this issue in Windows 7. The app is compiled for x86 platform only. Tries with "all platforms" too, same issue. I see two errors in the Windows Event Log

*错误1

应用:MyApplication.exe Framework版本:v4.0.30319   说明:该过程由于未处理的异常终止。   异常信息:异常code 0000005,异常地址071116C0

Application: MyApplication.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 071116C0

*的的错误2 * 的

*Error 2 *

错误的应用程序名称:MyApplication.exe,版本:1.1.2009.130,   时间戳:0x4e7b4051错误模块名称:未知,版本:   0.0.0.0,时间戳:00000000异常code:0000005故障   偏移:0x071116c0出错进程ID:0xa14错误应用程序   开始时间:0x01cc793091b8b5b0错误应用程序路径:   C:\ MYAPP \ MyApp的\ BIN \ 86 \调试\ MyApplication.exe错误模块路径:   未知报告编号:d351c329-e523-11e0-a2de-0023240631a8

Faulting application name: MyApplication.exe, version: 1.1.2009.130, time stamp: 0x4e7b4051 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x071116c0 Faulting process id: 0xa14 Faulting application start time: 0x01cc793091b8b5b0 Faulting application path: C:\MYApp\MyApp\bin\x86\Debug\MyApplication.exe Faulting module path: unknown Report Id: d351c329-e523-11e0-a2de-0023240631a8

任何指针来解决这个问题是高度鸭preciated。

Any Pointers to Fix this issue is highly Appreciated.

感谢

推荐答案

找到了解决困难的方式。我们需要设置uiaccess =在清单如此。设置在此发。需要注意的是,这是很烦人因为有很多解决此溶液的限制。但是,它的工作原理,但。欢迎到x64的世界。

Found a solution hard way. We need to set uiaccess=true in the manifest. Guidance is provided on this thread. Caveat is that it is very annoying as there are lot of restrictions around this solution. But it works though. Welcome to the world of x64.

感谢大家谁表现出兴趣这个问题,并试图找到我的一个解决方案。我很自豪能成为这个社会谁关心我们每个人的一部分。

Thank you all who showed interest in this issue and tried to find a solution for me. And I am proud to be part of this community who cares for each of us.