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
Be sure to check out & bookmark our Everything you need to know about electronic filing page. View the site.
Be sure to check out & bookmark our Everything you need to know about electronic filing page. View the site.
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
- :
- Database Corruption
Database Corruption
Options
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
TGDonovan
Level 2
Saturday
- Mark as New
- Permalink
- Report Inappropriate Content
I have had the individual database get corrupted multiple times this week. It appears to happen when doing a SDK access to the data. I was querying (no writing) the DATA1-Client Info table, and the database got reset to blank and a PTDATAI24.DB.001 file is created (which is the valid database), but the PDFDATATI24.DB file is down to 628kb and no clients show in Lacerte.
Based upon the timestamp of the database, I am certain that I was the only one accessing the system and the only access I was doing was a read of DATA1 Client Info. Does trying to switch years potentially cause the problem?
1 Comment 1
TGDonovan
Level 2
yesterday
- Mark as New
- Permalink
- Report Inappropriate Content
The problem appears to be related to my trying to access more than one year of Data1 from the same instance of an application. I know last tax season my application was able to do that (whether that was the intended implementation of the driver or not) but this year it can't access two different years and when it couldn't read the dataset (ODBC connection) the failure seemed to cause the database problem.