Solutions to MapX Problems

MapX has encountered many problems recently,

First question

ProgramWhen a permanent table is added to a layer

Address 73d37576 in mfc42.dll can not write at address 00000008 was probably written in this way, but it was not copied at that time.

I started to suspect that MapX was not installed correctly. reinstall it. If you suspect that the system is faulty, reinstall the system. Machine hardware, but not machine.

The size of the file generated after each error is found to be abnormal. The size is the same as the size after generation. The size of the newly created layer is either 0 or 1, check whether the file is not deleted when the file is deleted. The result remains the same after the file is deleted for 5 seconds. After analyzing the cause, we found that the size of the compressed package generated by a colleague was not normal. Suppose there is a conflict between compression and deletion. Verify and annotate the compression process. The result program is normal.

Check the program carefully and find that the process of compressing the original file is performed before deleting the file in the directory. As a result, the file may be deleted when it is being compressed, the deletion and compression operations are not normal.

The problem lasted for seven hours. I hope to save some time for people like me later.

 

The second question.

Note that you must end with endaccess when using beginaccess to improve efficiency. Otherwise, files will be occupied by programs when the data volume is large. When I first wrote a program, I did not pay attention to writing endaccess into beginaccess. As a result, the system encountered a problem and could not compress the file, prompting that the file was being occupied by a program. Due to lack of experience, I did not expect it to be the problem.

 

Next, add (to be continued)