Recently, I have encountered a lot of problems when using Mapx.
first question
The program is reported when running to the layer to add a permanent table.
Address 73D37576 in mfc42.dll can not write at address 00000008 probably written, did not copy it at the time.
Start suspecting is the mappX is not right, reload, can't. Doubt system has problems, reload, can't. Machine hardware, change the machine, no.
Slowly discovering an error, each of the files generated later is not normal, the size and the size of the size are consistent, and the newly created layer size is either 0. Eight or 1, seize this problem, verify that the file is not deleted I didn't delete it, so I paused 5 seconds after deleting the file, the result is still the same. Analyze the reasons, it is found that there is a colleague generated compression package size is not normal. Inspector is not compressed and deleted. Verify, annotation compression process. The result process is normal.
Carefully check the program, found that the process of compressing the original file is performed before deleting the directory, and then releasing the file again, the result is that the file may be deleted, making the deletion and compression is not normal.
This problem has been tossed for 7 hours before and after. I hope to save some time for people like me.
second question.
Note When using layer BeginAccess to improve efficiency, you must have to end with endaccess, otherwise, when the amount of data is large, the file will always be occupied. When you start writing a program, I didn't pay attention to write the endaccess as BeginAccess. The result has caused the problem. It doesn't compare the file. The prompt file is being occupied by a program. Due to the insufficient experience, it did not expect it to be the problem.
After the day, I will make up (forcession)
