|
We use dynamicube v2.5 control in a vb6 hosted application and have done for many years.
.cub files are refreshed on a daily basis using an in house update program which essentially performs the following methods:
Form1.DCube1.Load cubFile
Form1.DCube1.RefreshData
Form1.DCube1.Save cubFile, 1
This has worked with no problems (for several years) up until around 12 months ago. Since then we experience an occassional corruption. The corruption manifests itself as a cub file with a smaller file size which when loaded into DCube displays as a blank with no data showing.
We have improved our update process by restricting the update to a single cub file and then exiting the process as we were not sure if it was down to a VB6 memory leak. After doing this the process seemed to work for several weeks. Then the other day the problem re-occured. Our improved error reporting showed up the following error:
UpdateCubeList Error Processing File I:\Magicubes\Account Analysis\AA_CCY_EPI.cub Number:-2147467259, Description:Can't open ADO recordset
[ Extended Info :Can't open ADO recordset -2147217900 [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near the keyword 'from'. Source:Microsoft OLE DB Provider for ODBC Drivers], Source=DCube Class
If one loads up the corrupted file into our update app the error occurs on RefreshData giving the error above even though the syntax for the sql statement is perfectly valid ie. DCRecordSource : "select * from vw_aa_epi_cgbp"
When ever the problem occurs we repeat the update on a known good version and generally this works ok.
Our management are concerned that one day the repeated update will fail continually and we will be left high and dry without a functioning cub which would be disastrous to our business. We have tried every which way to discover why the cub fails but to no avail.
Has anyone else experienced similar behaviour and what did they do?
|