Our production part audit programs use a subroutine that sends a DataPage Spreadsheet report to a .txt file, which then goes to an Excel spreadsheet to display run charts. DP must be running to send the report.
Earlier this week, one of our machines started throwing me out of DP, displaying this message: “DataPage has encountered a problem and needs to close. We are sorry for the inconvenience.” This happened with every run of a part. (The other machine keeps measuring parts and sending reports with no issues.) After archiving the database and deleting tons of data, the problem went away – for a while. Now it kicks me out every third part. My response is to ‘unlock database’ (in DP Editor) and delete xstats11.tmp if needed. It is almost always 0KB file size. Then ctrl-U at the ‘statson’ line and everything is back to normal. For three parts.
You can try c/datapage/ open the folder your reports are in and Delete all files in the database directory with the following extensions
.dbl
.dbu
.dbx ( these file will regenerate)
.log
.taf
You should be left with files which have the following extensions
.k01
.k02
.d01
.d02
.d03
.d04
.d05
.dbd
It deletes the xstats file after every dump in DP...the directories will be a lil different depending on the version....I put at the beginning of all my progs....haven't had one single problem in 2 years..running 24/7 since doing this
Thanks, JM. xstats11 doesn't apprear to be the issue here, but we could add your routine to a prog to see if it helps.
pniven: There are 216 files named "VDM***.tmp also in the datapage folder, all 0KB. The oldest is 7/7/2005 and tne newest 10/26/2008. Can these be deleted without creating problems? Should the files you listed be the only files left in the folder?
OK. Now I am confused (no wisecracks, please). Ran two parts this AM, thrown out of DP. So I rebooted, unlocked d/b, ran two more parts and kicked out again. Checked xstats11 (0KB), unlocked d/b, and continued as described before. Part #10 is now running since that last DP exit with no problems. WTF? Not complaining, just puzzled.
Also, exited that prog, ran a part in a different prog, then reopened the first prog and continued with my study.