Welcome back! Ask questions, get answers, and join our large community of tax professionals.
- Topics
- Training
- Community
- Product Help
- Industry Discussions
- User Groups
- Discover
- Resources
Intuit Biz e-filing closure on December 21 at 6:00PM PST. Select your product for more Hot topics. Lacerte | ProConnect | ProSeries
Intuit Biz e-filing closure on December 21 at 6:00PM PST. Select your product for more Hot topics. Lacerte | ProConnect | ProSeries
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Intuit Accountants Community
- :
- User Groups
- :
- Lacerte SDK Group
- :
- Lacerte SDK - error reading TSJ field when the value is K?
Lacerte SDK - error reading TSJ field when the value is K?
Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
phillyj
New Member
09-29-2022
11:50 AM
- Mark as New
- Permalink
- Report Inappropriate Content
Getting an ODBC exception when trying to read Lacerte data using the SDK - Trying to read TSJ field where the value is K, and it's failing because that's not an expected value for the field. Any ideas?
Reply
2 Comments 2
Mark Patterson
Level 1
09-30-2022
10:11 AM
- Mark as New
- Permalink
- Report Inappropriate Content
I don't know if this is your problem or not, but I believe the latest Lacerte update broke the ODBC connector and we're waiting for an updated one from Lacerte. Current version is 1.0.0.335
https://developer.intuit.com/app/developer/lacerte-sdk/docs/lacerte-get-started
For any Sureprep users, it also broke the connection between Sureprep and Lacerte.
Reply
Steffan
Level 2
09-13-2023
07:52 PM
- Mark as New
- Permalink
- Report Inappropriate Content
I was getting this error using SDK version 1.0.0.347 when trying to access clients in the Partnership module. Only 11 clients would trigger this error.
I decided to update to the latest SDK to see if it would solve the error, but unfortunately the latest SDK seems to be broken entirely when querying the information I need in the partnership module.
Just my luck...