Skip to main content
Steffan
Level 4
September 14, 2023

Read_Data_Error in C3_3 column

  • September 14, 2023
  • 4 replies
  • 37 views

Hi all,

After upgrading to the latest SDK (1.0.0.356) I am receiving multiple different errors when trying to access data in the Partnership module.

For example, a simple query such as

SELECT C3_3 FROM [CLIENT#-Detail-ClientStateInfo]

 Fails with: "[Lacerte] (0) Read_Data_Error in C3_3 column: Error getting data for Column: C3_3. EAccessViolation: Access violation at address 0463F346 in module 'ClientDataAccess.dll'. Read of address 00000000"

I also occasionally get errors for the DATA2 table and any column in the DATA3 table.

This problem did not exist in version 1.0.0.347 of the SDK.

Is anyone else able to reproduce?

Thanks,

Steffan

    This topic has been closed for replies.

    4 replies

    Level 6
    September 14, 2023

    (I don't even have PAR module connected for TY2022, but achieve similar results in IND.)

    What year are you in?  In TY2022, I no longer have a Data2 table ("dependents" in IND module, "beneficiaries" in FID, "partners" in SCO PAR COR), because they re-structured how they handled that information.  It got split out from One Big Table (for all clients, lots of records) into individual tables (one per client, only that client's records).

    .

    I'm using Paradox, and most of the time deal with just one client at a time--I only need to "extract all detail from all clients" so many times during the course of a year--so I go to a File Open dialog and choose the one that I want.  I am also on v.356.
     - "Client#-Detail" I am able to open just fine, and see the several columns.
     - "Client#-Detail-SubClientInfo" ("children", what used to be in the overall Data2 table) opens & I view just fine.)
     - I am completely unable to open either of "Client#-Detail-ClientStateInfo" or "Client#-Detail-SubClientStateInfo"; each of them gives me a "key violation" error when I try.

    .

    For "Client#-Detail-ClientStateInfo", I get these errors (each on its own screen, I just right-arrow through them), in order left-to-right, top-to-bottom:
     

     

    Looks like the space limitation means that I get to read the memory address in the second half of each message, and multiple fields are throwing out "issues".



    Robert

    Level 6
    September 14, 2023

    "left-to-right, top-to-bottom"

    By which I mean to "read down through the leftmost column, then down through the center column, then down through the rightmost column."  Not "read it like a book, across the line then down to the next."
      Sorry.