July 27, 2012
This will probably be old news to most of you, but there’s always new people getting exposed to Clarify, so I figured it couldn’t hurt to share. If you’ve worked with the Clarify Classic Client for any amount of time (say, more than a day), you’ve probably run into the scenario where things start to misbehave. Often, this is because the Clarify cache files get corrupt. The fix is to delete those cache files, and restart the app. The cache files will get rebuilt during app startup. What gets cached? Mostly what gets cached is: Schema (data from the ADP tables) is cached in the <databaseName>.0XX file, where XX is your schema revision. Example: testdb1.062 Forms and other metadata is cached in the <databaseName>.cfy file. Example: testdb1.cfy ClearBasic Code is cached in a boatload of files in the CBCache directory…
Clearing Clarify Cache Files
July 27, 2012
This will probably be old news to most of you, but there’s always new people getting exposed to Clarify, so I figured it couldn’t hurt to share. If you’ve worked with the Clarify Classic Client for any amount of time (say, more than a day), you’ve probably run into the scenario where things start to misbehave. Often, this is because the Clarify cache files get corrupt. The fix is to delete those cache files, and restart the app. The cache files will get rebuilt during app startup. What gets cached? Mostly what gets cached is: Schema (data from the ADP tables) is cached in the <databaseName>.0XX file, where XX is your schema revision. Example: testdb1.062 Forms and other metadata is cached in the <databaseName>.cfy file. Example: testdb1.cfy ClearBasic Code is cached in a boatload of files in the CBCache directory…