ADODB, ASP.NET and Crystal Reports for VS 2010


not sure if in best place, or why first part has switched small font!

nb - i've raised 'crystal report' issue in sap forum, if unable address side of issue, can @ least address specific question

"does lack of support adodb extend corresponding odbc access method (rdo)?"

we have asp.net application written many years ago, , upgraded number of times. built under vs2010 32-bit application. application consists of vb code , lot (100+) of embedded crystal reports (using cr vs2010).

the application seems rock solid when installed on windows 2003. however, when running on windows 2008 r2 (as 32-bit app appropriate iis settings) getting intermittent crashes in w3wp process. raised incident ms , submitted dump files, , received following response:-

"the av happening @ com, oleau32.dll, module part of com plumbing.

i hate bearer of bad news, application asp.net 4.0 application using adobd pia assembly shipped visual studio 2005, unfortunately, not supported in server side application such asp.net , , has not been recommended usage  anymore microsoft."

our application vb code, developed on several years, has mixture of 'legacy' adodb code , ado.net code, looking @ upgrading adodb ado.net.

my question, however, relates crystal reports, use 'pull' model data ms sql databases via oledb.

as far sap concerned, have indicated should able use either 'pull' method (oledb or odbc), or 'push' method (ado.net datasets), though have said if use ado.net datasets, should limit size ('no more few thousand rows), concern crystal may using adodb 'pull' data. 

does lack of support adodb extend corresponding odbc access method (rdo)?

is implication of microsoft's response not recommend use of crystal reports 'pull' method in asp.net applications? if so, have major implications us, 100+ reports converted 'push' ado.net datasets.

any idea why problems have started occur on windows 2008 (r2)? application has been running without issues @ least 10 years on earlier server environments.



adodb has never been supported used in .net applications (not asp.net ones). this warning dates way .net 1.0. 

rdo not part of ado, com wrapper of oledb, a com wrapper of odbc. although non-support of ado in managed code not extend rdo, i don't think there effort test rdo's compatibility .net still not supported in managed code. supported along vb6 runtime on windows 8/2012, windows 2008 , r2 fine if calling native application. 

as sap's side, if remember correctly com support has been deprecated long time ago, cr vs2010 should native .net component. not sure how data component without ado.net.

because rdo com wrapper of odbc, suggest small odbc application see if problem mysql odbc driver or rdo wrapper.



visual c++ mvp






.NET Framework  >  Common Language Runtime Internals and Architecture



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

job syspolicy_purge_history job fail in sqlserver 2008

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'