Post reply

Help with data conversion resulted in overflow...

  • August 8, 2007 at 3:47 pm

    #197235

    Hello,

    Can somebody please help me I have the following table:

    CREATE TABLE [dbo].[DOCUMENTO_ACCESO_USUARIO] (

    [CODIGO_DOCUMENTO] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,

    [NUMERO_EDICION] [int] NOT NULL ,

    [CODIGO_ACCESO] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,

    [USUARIO_GRUPO] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,

    [COMPLETADO] [int] NOT NULL

    ) ON [PRIMARY]

    GO

    ALTER TABLE [dbo].[DOCUMENTO_ACCESO_USUARIO] WITH NOCHECK ADD

    CONSTRAINT [PK_DOCUMENTO_ACCESO_USUARIO] PRIMARY KEY CLUSTERED

    (

    [CODIGO_DOCUMENTO],

    [NUMERO_EDICION],

    [CODIGO_ACCESO],

    [USUARIO_GRUPO]

    ) ON [PRIMARY]

    GO

    ALTER TABLE [dbo].[DOCUMENTO_ACCESO_USUARIO] ADD

    CONSTRAINT [FK_DOCUMENTO_ACCESO_USUARIO_ACCESO] FOREIGN KEY

    (

    [CODIGO_ACCESO]

    ) REFERENCES [dbo].[ACCESO] (

    [CODIGO_ACCESO]

    ),

    CONSTRAINT [FK_DOCUMENTO_ACCESO_USUARIO_DOCUMENTO] FOREIGN KEY

    (

    [CODIGO_DOCUMENTO],

    [NUMERO_EDICION]

    ) REFERENCES [dbo].[DOCUMENTO] (

    [CODIGO_DOCUMENTO],

    [NUMERO_EDICION]

    )

    GO

    When I issue a select * against it from PowerBuilder 6.0/6.5 Data Manipulation Grid, I get the following message:

    select-error: Data-conversion resulted in overflow.

    Here is the current data stored in this table (header included)...

    CODIGO_DOCUMENTONUMERO_EDICIONCODIGO_ACCESOUSUARIO_GRUPOCOMPLETADO

    IT00001101TEST0

    IT00001102CRODRIGUEZ0

    IT00001102RMEDINA1

    IT00001103RMEDINA0

    IT00001104RMEDINA0

    IT00001105CRODRIGUEZ0

    IT00001105RMEDINA0

    MA00001101TEST0

    MA00001102RMEDINA1

    MA00001103RMEDINA0

    MA00001104RMEDINA0

    MA00001105RMEDINA0

  • August 8, 2007 at 8:02 pm

    #725582

    Hi !!! Somebody ? Anybody ?

    Thanks,

  • August 8, 2007 at 10:00 pm

    #725600

    I don't use Power Builder so this will likely not be much help... but, if it were me, I'd select 1 column at a time to troubleshoot which column is the likely offender and then go from there.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply