The job which converts the onix/xml update files unnecessarily increases the database size when an update file is imported.
The increase is mysterious and far larger than the size of the update file: An XML file with the size of 10mb and about 2.500 records results in an increase of 500mb in the Access file. Meaning that if we process 3 XML files, Access crashes because it reaches the physical limit of 2gb.
We have done some Googling on the possible cause for the bloating and it seems that it can be prevented by calling queries and/or objects in a different way. For example: [url removed, login to view]
So my request is to adapt the job in such a way that size-efficiency is accounted for.
My request is to have the new version of the job ready on January 4th, or, if that is not possible, let me know a committed date in the week after.
NB. we have made some changes in the job-code in the past period! So I attach the latest version of the code for you to use.