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.
Data goes to the xstats11.tmp file. From there I am assuming a utility of some kind sends it to Datapage's database. I am only assuming it is some type of utility as Datapage does not have to be running for this to take place. Perhaps that is where QC-Calc differs. It sounds to me like QC-Calc imports this data. With Datapage, after the info is transferred to the Datapage database the xstats11.tmp file is either emptied or deleted. It is when there is some kind of failure to upload the data to Datapage's database that problems occur. Partial and appended data in the xstats11.tmp file exasperates this problem and the transfer of data will not take place. The file needs to be emptied or deleted. Unfortunately I do not know the ins and outs of Datapage enough to know exactly what is going on that causes this. Like many others all I know is deleting the xstats11.tmp file fixes it. If an xstats11.tmp file exists when PCDMIS is done measuring a part it appends the data to that file, if it is trashed then you get an error trying to update the database. If there is no xstats11.tmp file PCDMIS creates a fresh one. The file that gets deleted is useless, it either contains junk or nothing at all so with Datapage there is no consequence to deleting it. It can't hurt so it only serves to help, QC-Calc I can not speak for. I recommend this only to users of Datapage. Actually I recommend to users of Datapage to not use Datapage but let's face it there are a lot of people using it. As a product, it will be gone soon that is my prediction anyway. I have little faith in the future of Datapage but there are many seats of it out there and will continue to be in service for a long time so if you must use it this code in each program (at the beginning mind you) will save some headaches.
If you put that code in a standalone program then that program will have to be executed once every time before you execute your program for measuring a part. Either that or you will have to put it into a sub in a standalone program then in every part program call that sub. It is probably best to just put it in every program.
Data goes to the xstats11.tmp file. From there I am assuming a utility of some kind sends it to Datapage's database. I am only assuming it is some type of utility as Datapage does not have to be running for this to take place. Perhaps that is where QC-Calc differs. It sounds to me like QC-Calc imports this data. With Datapage, after the info is transferred to the Datapage database the xstats11.tmp file is either emptied or deleted. It is when there is some kind of failure to upload the data to Datapage's database that problems occur. Partial and appended data in the xstats11.tmp file exasperates this problem and the transfer of data will not take place. The file needs to be emptied or deleted. Unfortunately I do not know the ins and outs of Datapage enough to know exactly what is going on that causes this. Like many others all I know is deleting the xstats11.tmp file fixes it. If an xstats11.tmp file exists when PCDMIS is done measuring a part it appends the data to that file, if it is trashed then you get an error trying to update the database. If there is no xstats11.tmp file PCDMIS creates a fresh one. The file that gets deleted is useless, it either contains junk or nothing at all so with Datapage there is no consequence to deleting it. It can't hurt so it only serves to help, QC-Calc I can not speak for. I recommend this only to users of Datapage. Actually I recommend to users of Datapage to not use Datapage but let's face it there are a lot of people using it. As a product, it will be gone soon that is my prediction anyway. I have little faith in the future of Datapage but there are many seats of it out there and will continue to be in service for a long time so if you must use it this code in each program (at the beginning mind you) will save some headaches.
If you put that code in a standalone program then that program will have to be executed once every time before you execute your program for measuring a part. Either that or you will have to put it into a sub in a standalone program then in every part program call that sub. It is probably best to just put it in every program.
