Skip to main content

[archive] Acu4GL for MS SQL 8.0 and "bigint"

  • February 25, 2009
  • 2 replies
  • 0 views
D

[Migrated content. Thread originally posted on 17 February 2009]

Hi,

We have just installed Acu 4GL for MSSQL and the customer is using MS Access to access their data.

It appears Acu4GL 8.0 for MSSQL is mapping PIC 9(12) fields to bigint values in SQL Server. This is all correct and doesn't cause any problems naively but an error in Access means that any table with a bigint can't be opened in MS Access.

I'm 99% sure Acu 4GL 7.x converted PIC 9(12) to DECIMAL(12,0) values and this worked correctly in MS Access.

I know this is 100% a Microsoft bug in MS Access, but are there any ways to force Acu4GL to create DECIMAL fields instead of bigint fields?

Thanks,

Ray

Note: The bug I'm talking about is described at:
http://support.microsoft.com/kb/321901/en-us

    2 replies

    D

    [Migrated content. Thread originally posted on 17 February 2009]

    Hi,

    We have just installed Acu 4GL for MSSQL and the customer is using MS Access to access their data.

    It appears Acu4GL 8.0 for MSSQL is mapping PIC 9(12) fields to bigint values in SQL Server. This is all correct and doesn't cause any problems naively but an error in Access means that any table with a bigint can't be opened in MS Access.

    I'm 99% sure Acu 4GL 7.x converted PIC 9(12) to DECIMAL(12,0) values and this worked correctly in MS Access.

    I know this is 100% a Microsoft bug in MS Access, but are there any ways to force Acu4GL to create DECIMAL fields instead of bigint fields?

    Thanks,

    Ray

    Note: The bug I'm talking about is described at:
    http://support.microsoft.com/kb/321901/en-us
    There is no way that I'm aware of to cause Acu4GL to map a pic 9(12) to decimal (12,0).

    However the $XFD BINARY directive will cause it to be mapped as binary. It's worth a try.
    D

    [Migrated content. Thread originally posted on 17 February 2009]

    Hi,

    We have just installed Acu 4GL for MSSQL and the customer is using MS Access to access their data.

    It appears Acu4GL 8.0 for MSSQL is mapping PIC 9(12) fields to bigint values in SQL Server. This is all correct and doesn't cause any problems naively but an error in Access means that any table with a bigint can't be opened in MS Access.

    I'm 99% sure Acu 4GL 7.x converted PIC 9(12) to DECIMAL(12,0) values and this worked correctly in MS Access.

    I know this is 100% a Microsoft bug in MS Access, but are there any ways to force Acu4GL to create DECIMAL fields instead of bigint fields?

    Thanks,

    Ray

    Note: The bug I'm talking about is described at:
    http://support.microsoft.com/kb/321901/en-us
    There is no way that I'm aware of to cause Acu4GL to map a pic 9(12) to decimal (12,0).

    However the $XFD BINARY directive will cause it to be mapped as binary. It's worth a try.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement