Query - Error: Expression caused an overflow

Hello!

Im running a application with a SQL CE database on a PDA (Qtek S200 and Qtek 2020i). Running the SQL CE version 3.1.

When querying the database with this question

SELECT Sum(Units) as sumUnits, tWorkReport.CreatedDate, tWorkReport.ModifiedDate FROM tWorkReport LEFT JOIN tWorkReportRow ON tWorkReport.WorkReportID = tWorkReportRow.WorkReportID WHERE 1=1 AND tWorkReport.PersonID = 160 GROUP BY tWorkReport.WorkReportID,GroupNr,ReportDate,PlantsPerUnit, tWorkReport.CreatedDate, tWorkReport.ModifiedDate ORDER BY ReportDate DESC

I get the error: Expression caused an overflow [,,, Name of function (if known),,] Native Error: 25901

A weird thing is that it has worked fine for a long time. After doing an update (adding records) to a table we got this error. The table that was updated has nothing to do with the SQL-query.

A temporary workaround for this was just write it "Sum(Convert(INT,Units) as Sumunits" but this means that Units with the format as decimal looses its decimals when converting to integer.

I came a across this error once before when doing development on the application - a workaround then was to write the sum like this " 1 - Sum(Units) - 1 as Sumunits" , this did not work in the latestest question.

I have tried breaking down the query to find where i get the error and it is the Sum function that gives this error.

Anyone else that has come across this error? Bug? Any workaround? The convert to int is just a temporary solution i want to use decimals!

Anyone? |||

Im still having this problem and havent got any solution yet. Reporting to Microsoft tomorrow.

Query - Error: Expression caused an overflow

Hello!

Im running a application with a SQL CE database on a PDA (Qtek S200 and Qtek 2020i). Running the SQL CE version 3.1.

When querying the database with this question

SELECT Sum(Units) as sumUnits, tWorkReport.CreatedDate, tWorkReport.ModifiedDate FROM tWorkReport LEFT JOIN tWorkReportRow ON tWorkReport.WorkReportID = tWorkReportRow.WorkReportID WHERE 1=1 AND tWorkReport.PersonID = 160 GROUP BY tWorkReport.WorkReportID,GroupNr,ReportDate,PlantsPerUnit, tWorkReport.CreatedDate, tWorkReport.ModifiedDate ORDER BY ReportDate DESC

I get the error: Expression caused an overflow [,,, Name of function (if known),,] Native Error: 25901

A weird thing is that it has worked fine for a long time. After doing an update (adding records) to a table we got this error. The table that was updated has nothing to do with the SQL-query.

A temporary workaround for this was just write it "Sum(Convert(INT,Units) as Sumunits" but this means that Units with the format as decimal looses its decimals when converting to integer.

I came a across this error once before when doing development on the application - a workaround then was to write the sum like this " 1 - Sum(Units) - 1 as Sumunits" , this did not work in the latestest question.

I have tried breaking down the query to find where i get the error and it is the Sum function that gives this error.

Anyone else that has come across this error? Bug? Any workaround? The convert to int is just a temporary solution i want to use decimals!

Anyone? |||

Im still having this problem and havent got any solution yet. Reporting to Microsoft tomorrow.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QA Setup question

I know that this is just a very small point, but it bugs me and I
wonder if there is a work around. When I use an old version of QA
(version 8.000.194) keywords are properly highlighted. When I run a
more recent version (8.000.760), some are, but some (FROM, WHERE, AND,
etc) are not. Is there a fix for this? Thanks.
-Johntry going to Tools-->Options-->Fonts
Then select keyword in the colors panel and set it to the correct
color, see if that helps
http://sqlservercode.blogspot.com/|||"SQL" <denis.gobo@.gmail.com> wrote:

>try going to Tools-->Options-->Fonts
>Then select keyword in the colors panel and set it to the correct
>color, see if that helps
>
That's exactly what I'm doing and I'm not getting the color change on
come keywords.
-John|||Can you try clicking "reset all".
"John Baima" <john@.nospam.com> wrote in message
news:gltns1dcib24om49o5m32jmme5m7jje3c9@.
4ax.com...
> "SQL" <denis.gobo@.gmail.com> wrote:
>
> That's exactly what I'm doing and I'm not getting the color change on
> come keywords.
> -John
>|||"Raymond D'Anjou" <rdanjou@.canatradeNOSPAM.com> wrote:
>Can you try clicking "reset all".
>"John Baima" <john@.nospam.com> wrote in message
> news:gltns1dcib24om49o5m32jmme5m7jje3c9@.
4ax.com...
No, that does not change anything. Again, some keywords are
highlighted, but not all. The versions are different. What is the
latest and greatest version number for QA'
-John|||John Baima (john@.nospam.com) writes:
> I know that this is just a very small point, but it bugs me and I
> wonder if there is a work around. When I use an old version of QA
> (version 8.000.194) keywords are properly highlighted. When I run a
> more recent version (8.000.760), some are, but some (FROM, WHERE, AND,
> etc) are not. Is there a fix for this? Thanks.
In another case I heard of this, no words were highlighted. The suggestion
then was to run
regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqllex.dll"
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Erland Sommarskog <esquel@.sommarskog.se> wrote:

>John Baima (john@.nospam.com) writes:
>In another case I heard of this, no words were highlighted. The suggestion
>then was to run
> regsvr32 "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqllex.dll"
That was a little scary, but it did the trick! Thanks!
-John