Settings for the File Checker and Copier

Manage Settings

This form lets you build up one, or several, sets of settings. They are saved in "FileCheckerAndCopier_Settings.xml" in the same folder as the application.  New, Copy, and Delete work as you would expect with Save All required to save the changes. Use Save All before you select a different setting set to edit.

General Settings


  • Parameter set name: A descriptive name for your benefit
  • Maximum documents in memory: Prevents the FCC trying to read all data in at once by limiting it to the first 1000, second 1000 etc*
  • Screen refresh: Every 50 records is ok for the Copier, but every 500 or 1000 is better for the Checker as it can be very fast
  • Too many errors: The first time you run it you may get a large number of errors that are due to some factor you can control, eg security settings hiding documents, so having it stop if there are a lot of errors can be useful
  • Document number range: The range of document numbers to check. When getting started set it to a small range to make sure everything is working before upping the ante*

* The FCC operates by selecting the first 1000 documents, then the second 1000, and so on through the range of document numbers. The SQL for this is set in 3. Data Source

File Copy and Rename Settings


  • Copy folders: The EDMS database will hold the path to the actual documents. The actual document tree will probably start a little down the tree. These two settings allow you to copy just the relevant part of the tree. Note there is no “\” at the end of each
  • Add extension: Some EDMSs store documents without a file extension. Ticking this and including the extension in the source SQL adds the extension.
  • Copy and rename: Note: This is disabled in the initial release but will be restored. If you want to rename the files as you copy them include the new name in the SQL and tick this.
  • Use placeholders: Your migration software probably will expect a file to exist so this option allows you to insert a “placeholder” in its place.You’ll need a placeholder file for each file type Eg Placeholder.doc, Placeholder.xls.
  • Overwrite: If you have done a copy run without placeholders , then found and restored a few of them, you can rerun it with overwrite off and it will only replace the missing files

Data Source Settings


and scroll on the form to see the rest of it.


  • Connection string: The OLEDB connection string for the database. Click on the "…" button to use the connection string builder. There is a known issue where the password contains a “;”. In that case you’ll need to fix it manually
  • Select Statement: This is built up from the selections made below.
  • Build and Test: Build combines the choices you have made into a working SQL statement for the application. Test brings up a new form which will bring back a few records to see if the SQL works.
  • Table: The table (or view) to select the data from
  • Required fields: These are the fields in your data source. Note the SQL renames them to DocNum, DocVer, and FilePath
  • File extension: Tick the box and enter the field name from your source data
  • Last Edit Date: Enter the field name. The tick box to say you wish to use this is in the “Where” clause section
  • Where clause: Tick the last Edit Date box to use it (having entered the field name above) and select the date to use
  • Where Clause custom additions: Best left for advanced SQL users. Whatever you enter will be bundled in brackets and appended with “AND”. You’ll see how it looks in the built SQL above.

Logging settings


  • Connection string: The OLEDB connection string for the database. Click on the "…" button to use the connection string builder. There is a known issue where the password contains a “;”. In that case you’ll need to fix it manually
  • Log table name: You’ll need to set the table up. There is no requirement to use the table name above. The script provided can be adapted to create the table.

Advanced settings


  • Be careful of this one. It does seem to be able to bend people’s minds.
  • If you are working off the live file store you don’t need to do anything
  • If you are working off a copy of the file store (safer if you have the storage space) then this is needed
  • In this case the EDMS database (whether the live one or a copy doesn’t matter) will have the locations of the files in the live file store, not the copy of the file store. So you need to tell the application to look for the files in the copy of the file store.

We do this by telling it to change the start of the file path, to replace the text at the start of the file path name provided by the database with the appropriate start for the location of the copy of the file store.