There’s another thread about this I think, the fix is to change the component set to the previous version ie 1.95.15904 (014) to do the export. I’ve done my own exporter using autoit which is about 4 to 5 x faster, if anyone wants to try it I could upload it somewhere?
We had a reply from Greta in another thread in this group:
The latest FIS known issues doc identifies an issue in FIS component set 015 which prevents ILR data being exported as an Access database file (MDB).
Providers are advised to use an older component set e.g. 014 to export ILR data to an Access database. Component set 015 only contains a fix to the amalgamation functionality so the impact of using the older component set is minimal.
It’s not fit for purpose, they probably tested on a top end pc with a tiny dataset.
In the short term they should have added a reduced export option, one which only did the fis database and excluded the LARS, large employers and postcode data. That would be so much faster and smaller, and quite easy to code.
The tasks are all in the manifest xml, the export is a collection of sub tasks.
I actually use the manifest to drive my autoit export script and use the sql scripts for the actual selections and write to a copy of the desktopservices.mdb found in the latest component set. A full export takes about 15 minutes on modest hardware, over and hour for the same export from the FIS. I’ve added options to just export the fis and other subsets too