I thought this would be nice for the first thread here. Any PCDMIS part program I have that saves stats I put this at the begining of. It looks for and deletes the xstats11.tmp file when executed. This avoids the way of doing it manually which is usually right after things screw up.
OK, that helps me understand how DP processes the data and the problems and I can understand why you would need to delete the as a matter of course when using datapage.
Then my advice earlier only applies to non-datapage data consumers. Jan_d said that he was going to use this with his Infinity and he may want to reconconsider untill he determines exactly how Infinity handles the data.
So, I guess bottom line, if your SPC program(including Datapage) uses xstats11 file in a non-accumulating way then using the delete method is a useful workaround.
Well, you can also use it as an accumulating way with Datapage. If you are running a 30-pc study, you can tell it NO when it asks if you want to update Datapage and the data will accumulate in the XSTATS11.TMP file until you DO tell it to update. You can wait until all 30 parts are checked, then update at the end. Myself, I would NEVER do this because you never know what kind of error will pop up and when and what will it do to the data. Also, if the beginning of the prgoram deletes that file, you will never get any data except the last part checked if you wait until you are done to update. HEY BOOGER-BOY, do you use an UPDATE command at the end of your programs to send 'force' the Datapage update so you don't lose your data?
OK, that helps me understand how DP processes the data and the problems and I can understand why you would need to delete the as a matter of course when using datapage.
Then my advice earlier only applies to non-datapage data consumers. Jan_d said that he was going to use this with his Infinity and he may want to reconconsider untill he determines exactly how Infinity handles the data.
So, I guess bottom line, if your SPC program(including Datapage) uses xstats11 file in a non-accumulating way then using the delete method is a useful workaround.
Well, you can also use it as an accumulating way with Datapage. If you are running a 30-pc study, you can tell it NO when it asks if you want to update Datapage and the data will accumulate in the XSTATS11.TMP file until you DO tell it to update. You can wait until all 30 parts are checked, then update at the end. Myself, I would NEVER do this because you never know what kind of error will pop up and when and what will it do to the data. Also, if the beginning of the prgoram deletes that file, you will never get any data except the last part checked if you wait until you are done to update. HEY BOOGER-BOY, do you use an UPDATE command at the end of your programs to send 'force' the Datapage update so you don't lose your data?
