Call: +44(0)20 7428 1255

Matchcode UK Changes

Release Y11M11

Matchcode UK Engine Version 5.2.26

  1. Updated to also read RCDB files with missing null terminators. (Bug #1275)
  2. Fix for when loading multiple RCDB files. (Bug #1236)
  3. Changed the format of the date on the database file from yyyymmdd to ddmmyyyy. (Bug #1310)

Matchcode 5 Server/Module Version 1.6.28

  1. Fixed a bug that caused mcserver to crash with long and complex input. (BUG #1025)
  2. Under FieldInfo, output only fields should not have more than zero on "Max Input Length".
  3. Fixed a bug for the Address Formatting feature where LineNumber parameter ignored blank lines and shift elements to the wrong line. (BUG #1329)

Release Y11M08

Matchcode UK Engine Version 5.2.25

  1. Added code to allow Capscan Data to be accessed from the internet.
  2. Changed click counting to use new methods.
  3. Fixed the problem where WAF settings for fixed width output did not count concatenate delimiters properly. (Bug #1006)
    E.g. ADDKEY,RESCODE,ADDR(FI=T,LC=4,CO=T,DE=MS,LL=80,FO=T,EL=T,PCD=EL:0,ORG=EL:0,TWN=FO:3,CNT=FO:4) from search where addr="UNIT 7, the glenmore centre, ME103GL"
  4. Changed code to prevent ambiguous results when a more complete address can be resolved. (Bug #551)
    E.g. 61 Main Street, Castleisland, Kerry does not return ambiguity between 61 Main Street, Castleisland, Kerry and Main Street, Castleisland, Kerry

Matchcode UK Server/Module Version 1.6.27

  1. Linked with new version of the internal Address Formatting library .
  2. Linked with Matchcode 5.2.25.
  3. Fixed a bug so that when processing the address the delimiters are applied after single line output, and added checks for fixed length lines and double quotes and corrected string length calculation. (BUG #1142)
  4. Fixed the incorrect County(AC) field output when used with NSPDO.RCD and DISCTCNY.RCD. (BUG #1280)

Release Y11M05

Matchcode UK Engine Version 5.2.24

  1. Added the ability to have multiple sources for the same data, linked at different levels of detail, and be able to pick up the most accurate data available from the multiple sources. In order of preference the different levels are: Person Level, Household Level, Postcode Level.

Matchcode UK Server/Module Version 1.6.24

  1. Linked with new version of the internal Address Formatting library .
  2. Linked with Matchcode 5.2.24.
  3. Fixed a bug to show Hitcount, Hitlimit and DaysLeftToRun for standalone mode. (BUG #1108)
  4. Fixed a bug for Hit Counted licence issue with HP-UX (PA-RISC) and (IA64). (BUG #1139)

Release Y11M02

Matchcode UK Engine Version 5.2.23

  1. Trailing spaces in first part of qbrowse query meant second part was ignored. (Bug #1078)
    E.g. QBROWSE on "22 villa ,bingley" The space after 'villa' means 'bingley' is ignored.
  2. Server and Client crash when cross-matching on a pool with more than one PAF (Bug #1079)
  3. Fixed building name select after quick browse with invalid building number (Bug #872)
    E.g. Quick browse on "1000 KENTISH TOWN ROAD" followed by a select on building name "109A" now works.
  4. Improved click counting performance. (Bug #1094)
  5. Number taken off building name when concatenate is turned on. (Bugs #637, #668, #700, #993)
    E.g. SINGLE SEARCH on "ADVANCE YACHT SYSTEMS,SO14 5QF (QC)" will give "Advance Yacht Systems,Unit 3,Building,30,Lower York Street,SOUTHAMPTON,SO145QF1T". As the BUILDING NAME is "Building 30" it can be seen that the 30 has been split from the BUILDING NAME.

Matchcode UK Server Version 1.6.23.3

( linux-i386 , linux-i686 , Solaris-Sparc-8 , Solaris-Sparc-10 , HPUX-PARISC , HPUX-IA64 => Version 1.6.22 )
( TRU64 , solaris-X86 , AIX-PowerPC , Linux-x86_64 => Version 1.6.23 )

  1. Linked with new version 1.1.4 of internal library addfmt1.
  2. Linked with Matchcode 5.2.23.
  3. Fixed a crash caused by a memory leak in version 1.6.21 of the Matchcode Server when used with a Date Restricted License..

Matchcode UK Module Version 1.6.23.3

  1. Linked with new version 1.1.4 of internal library addfmt1.
  2. Linked with Matchcode 5.2.23.
  3. Fixed a crash caused by a memory leak in version 1.6.21 of the Matchcode Module when used with a Date Restricted License..
  4. Fixed an issue where logs were not being written to the log file. (Bug #1124)

Release Y10M11

Matchcode UK Engine Version 5.2.22.1

  1. Support loading more RCD files in a single pool. (Bug #941)
    E.g. Installing RCD files from every dataset no longer hits the RCD file limit.
  2. Fixed incorrect FieldStatus flag for locality (Bug #748)
    E.g. Return FieldStatus from Crossmatching "West Wing,Ditchley Park,Enstone,Chipping Norton,Oxon,OX7 4EP".
  3. Prevent invalid postcodes temporarily disabling PC Change functionality (Bug #957)
    E.g. Postcode AB1 0AA changed to AB13 0AA. Quick Browse "AB13 0AA" (the good postcode) or "AB1 0AA" (the changed postcode) should give the same result for both: 
        AMBIGLIST: MILLTIMBER BRAE, MILLTIMBER FARM
    ADDR: MILLTIMBER, ABERDEENSHIRE, AB13 0AA
    Quick Browse "AB1 0AA1A" (the invalid postcode) and then "AB1 0AA" (the moved postcode) used to give no results for both. Now returns "MILLTIMBER" address as above.
  4. NUMNOALPHA and NUMALPHACHANGE not considered (Bug #844)
    E.g. Previously if both NUMNOALPHA and NUMALPHACHANGE are enabled with a search for "69B Chardmore Road, London, N166JA" Matchcode will output the address associated with house number 69. (NB There is no 69B on this road just 69A and 69) Now it will produce an ambiguity list with 69A and 69.
  5. Fixed a problem where the length of PAF setting in spider.ini files causes file to not exist (Bug #922)
    E.g. If in spider.ini the setting for the paf file is the following PAF=D:\CAPSCAN_WORK\CAPSCAN_APP_INSTALLS\DATA_TEST\capscan.paf;D:\CAPSCAN_WORK\Capscan_App_Installs\DATA_TEST\MRDATA\MultipleResidence.paf The pool fails to start and you get the error message saying unable to open file, file doesn’t exist and naming the file as D:\CAPSCAN_WORK\Capscan_App_Installs\DATA_TEST\MRDATA\MultipleReside
  6. Click Counting. There is now an accurate counting of PAF hits. People with Use Restricted licences will have their PAF hits counted according to the current Royal Mail Pay Per Click rules.
  7. Fixed a crash that occurred when multiple databases are used. (Bug #1079)

Matchcode UK Server Version 1.6.20

  1. Linked with new version 1.1.3 of internal library addfmt1
  2. Linked with Matchcode 5.2.22.1
  3. Linked with Sortcode 3.1.9.1
  4. Fixed a bug that caused mcserver to crash with wrong search type. (Bug #845)
    E.g.: SELECT easting from xmatch where postcode=”BT487AS”"

Release Y10M06

Matchcode UK Engine Version 5.2.19

  1. Fixed issue where locality punctuation prevented Select from working. (Bug #940)
    E.g. Search on "DN6 7EJ" and Select any ambiguity will again return a result rather than just a postcode.

Matchcode UK Server Version 1.6.19

  1. Fixed an issue where grid coordinates were being corrupted on output (Bug #953)
  2. Linked with Matchcode 5.2.19

Release Y10M05

Matchcode UK Engine Version 5.2.18

  1. Fixed a missing building number after quick browse on "W1B1PE". (Bug #436)
    E.g. Quick browse on "W1B1PE" will now return building number "22".
  2. Fixed issue where "MERIDEN C OF E" was matching to "MERIDEN C OF E SCHOOL" when "MERIDEN C OF E PRIMARY SCHOOL, FILLONGLEY ROAD, MERIDEN, COVENTRY, WEST MIDLANDS, CV7 7LW" was cross matched. (Bug #776)
  3. Fixed issue where single list mode was broken by Y09M05. (Bug #737)
    E.g. Single search for addr,postcode and ambiglist(LF=S,LD=CL) with "SE16 3BB" for the input address.
  4. Fixed issue where no SIC or DUNS value is returned in Combined List Mode. (Bug #724)
    E.g. Single search for ambiglist(LF=C,LD=N),searchstatus,DUNS,SIC03,SIC03TEXT,addr and rescode. Then select the ambiguity "MOORE STEPHENS CHARTERED ACCOUNTANTS,12,WARWICK LANE,LONDON,EC4M7BP9Z" and no SIC or DUNS is returned.
  5. Fixed issue where AKMatchTop affects Cross Matching. (Bug #840)
    E.g. A search for "10 AUCHENKILNS HOLDINGS, CONDORRAT, CUMBERNAULD" with AKMATCHTOP in mcdparam.ini set to 0 will now return the correct address.
  6. Fixed issue which prevents crashes in rare circumstances. (Bug #901)
  7. Added check for multiple residency license.
  8. Punctuation will now be returned for dependent locality, locality and post town before an address is fully resolved. A full postcode will be needed to return punctuation for these elements. (Bug #684)
    E.g. Quick browse on "CM23 5RG" will now return post town "BISHOP'S STORTFORD".
  9. Punctuation will now be loaded for each database in use. This allows punctuation to be provided for a second database when multiple databases are loaded.
  10. Fixed the handling of delimiters longer than one character when line length is imposed. E.g. SELECT ADDR(LL=15,DE='#####',FO=1,CO=1,ORG=FO:1,SUB=FO:1,BLD=FO:1,BNO=FO:1,DST=FO:1,STR=FO:1,DLO=FO:1,LOC=FO:1,TWN=FO:1,CNT=FO:1,PCD=FO:1) FROM XMATCH WHERE ADDR="Capscan,NW1 9BB" produced "Capscan#####Grand U,,,,,," e.g. linelength 19 instead of 15 for line 1

Matchcode UK Server Version 1.6.18

  1. Linked with new version 1.1.1 of internal library addfmt1
  2. Linked with Matchcode 5.2.18
  3. Linked with Sortcode 3.1.7.2

Release Y10M02

Matchcode UK Engine Version 5.2.17.1

  1. Improved cross matching when addresses have a building with a similar name to the street. (Bug #658)
    E.g. Crossmatch on "2 Well Hill Cottages, Well Hill, Finstock, CHIPPING NORTON, Oxfordshire, OX7 3BU" will now match to "2 WELL HILL COTTAGES" instead of building "2" on the street "WELL HILL".

Matchcode Server Version 1.6.17

  1. Linked with Matchcode 5.2.17
  2. Linked with Sortcode 3.1.6
  3. Addition of NonPAF elements restricted to crossmatching to prevent duplication of elements (Bug #596)
    E.g. Crossmatch on "The City of Edinburgh Council,P O Box 23797,4 East Market Street,Edinburgh,EH8 8WR" will now match to "The City of Edinburgh Council,P O Box 23797,4 East Market Street,Edinburgh,EH8 8WR" and not "The City of Edinburgh Council,P O Box 23797,P O Box 23797,4 East Market Street,Edinburgh,EH8 8WR"

Release Y09M11

Matchcode UK Engine Version 5.2.16

  1. Fixed ambiguity list without ranges. (Bug #501)
    E.g. Do a Rapid Address Lookup on postcode RM18 8NH.
    You get an ambiguity list with each house number on a separate line.
    Select a house number then select a name.
    Then unselect and unselect again. You get back to an ambiguity list that isn't expanded.
    However it has two entries. These are {1..18} and {20..22)Evens.
    With the new fix the first ambiguity list i.e. The list of numbers will now be a ranged list
    i.e. {1..18} and {20..22)Evens.

  2. Additional sanity checking for corrupt data files.
    E.g. The following are examples of possible messages in the log file e.g. spider.log file.:

    Validation successful:
    Tue Nov 03 15:05:14 2009,Info,DSG_Check(),"File sanity check successful."

    Validation failed:
    Tue Nov 03 15:05:14 2009,HighLevel,DSG_Check(),"Datafile 'C:\CAPSCAN\UKDATA\CAPSCAN.PAF' does not have a valid signature sequence! It may be corrupt or incomplete."

    Signature check skipped:
    Tue Nov 03 15:05:14 2009,Info,DSG_SmartCheck(),"Signature check skipped."

Release Y09M08

Matchcode UK Engine Version 5.2.15

  1. Focusing up from a complete address would sometimes return an empty ambiguity list. (Bug #685)
    E.g. Crossmatch: "New Buckenham The Granary, Norwich Road, Norwich, NR16 2AS";
    Select: "Caistor St Edmund";
    Select: "Without Building Name";
    Focus: "Building Name".
  2. Fixed a bug that caused a floating point divide by zero error when using the Y09M05 PAF(Bug #706)
    E.g. Crossmatch "Uisge-Beartha, Tarlogie, TAIN, IV19 1QA"
    N.B.This only appears to cause a problem when the calling application is Delphi.
  3. Writing an INI file without a path would not use the current working directory. (Bug #665)
  4. When entering "136 Athlumney Castle,Athlumney,Navan,An Mhi" into Geodirectory an ambiguity list is returned for house numbers (1 - 45) and (47 - 246). This is now fixed (Bug #634)

Release Y09M05

Matchcode UK Engine Version 5.2.14

  1. Fixed a memory leak and the use of an uninitialised value in Quick Browse. (Bug #247)
    E.g. Running a batch job of Quick Browse searches showed the memory leak.
  2. Fixed an issue where Matchcode would use the county name as a town causing the county to be reported as missing. (Bug #635)
    E.g. Crossmatch on "45 chosen way,hucclecote,gloucester,glos,gl3 3bu" returned an ELEMS_MISSING value of 512 (COUNTY).
  3. Xmatching on High Street Crawley produced ambiguity list.(Bug #595)
  4. MSCORE not 100 in london when you add 'London' county(Bug #433)
    E.g. SELECT mscore from xmatch where addr="tandoori garden,98 lillie road,london,london sw6 7sr" produced MSCORE:84
  5. Modifications for 64 bit architecture.

Release Y09M02

Matchcode UK Engine Version 5.2.12

  1. Fixed an issue where Matchcode failed to match "Block D" on input with "D Block" on the database. (Bug #597)
    E.g. Crossmatch on "Flat 1, Block D peabody Estate, vauxhall bridge road, SW1V 1TE" now matches to "D Block".
  2. Fixed an issue where Matchcode would fail to match addresses with the building number stored in the building name field. (Bug #580)
    E.g. Quick browse on "10 CARYLLS COTTAGES,RH12 4SQ" no longer produces an ambiguity list.
  3. Fixed Random Server Crash during batch runs. (Bug #611)
  4. Changes made throughout in porting to 64bit Windows

Matchcode UK Engine Version 5.2.11.1

  1. Fixed a sporadic memory fault that was occurring intermittently with certain addresses. (Bug #591)
    E.g. Crossmatching " 19 G41 3BJ".
  2. Fixed a problem where higher, non-matching, address elements could get added to the top of an ambiguous address.
    E.g. Crossmatching "Turnpike Properties, Smalley Hall, Main Road, Ilkeston, DE7 6DS". Only one of the ambiguities should have 'Gardeners Cottage' in the address

Release Y08M11

Matchcode UK Engine Version 5.2.10.3

  1. Quick browse by postcode ignored building names/numbers (Bug#606)
    E.g. Postcode search for "THE LATCH,PA113DR" failed.
  2. The function num_from_str() reports the wrong errno code. (Bug#612)
    E.g. 22 Baker Street,0123456789012345,London,W1U 3BW causes errno to get set to ERANGE (34) after the MCD_MatchCode() call

Release Y08M08

Matchcode UK Engine Version 5.2.9.3

  1. Too long an input line caused problems (Bug #590)
    E.g. Crossmatching "G A ROBSON & SON MR T J, MR G A & MRS E A ROBSON T/A","CARLTON HUSTHWAITE","THIRSK","YO7 2BP".
  2. Too many words in a line caused a crash (Bug #589)
    E.g. Crossmatching "G S B - I N T E R N A T I O N A L - LTD,NOTTING HILL,LONDON,W11 4HE", caused a crash.
  3. Bug 594 - Scribbler Fix in cdmatcht.c (Bug #594)
  4. Bug 584 - Scribbler in cdmatcht.c (Bug #584)
    E.g. With Geodirectory data, crossmatch of "105 QUINAGH GREEN","QUINAGH","CARLOW" causes the Scribbler to take effect and write to memory outside of an array.
  5. Fixed an issue where QuickBrowse on "the" was producing error messages in spider.log (Bug #559)
    E.g. QuickBrowsing on "the" produces an error message in the log of previous versions.
  6. Fixed an issue where Matchcode was failing to add non-paf elements. (Bug #567)
    E.g. Crossmatch on "61 ashfield place,aberdeen,AB106QJ" now adds more elements from the input.
  7. Fixed an issue where Matchcode was failing to return address elements in combined list mode. (Bug #569)
    E.g. Crossmatch on "stobhill general,133 balarnock road,glasgow,g21 3uw" using combined list mode now returns "133" as a building number.

Release Y08M05

Matchcode UK Engine Version 5.2.8.1

  1. Fixed a bug where QuickBrowse on "2a,EX2 5HY" was producing strange ambiguity lists (Bug #537)
    E.g. QuickBrowsing on "2A,EX2 5HY" produces an ambiguity list which is the same list that you would get if you browse on just the postcode.
  2. Fixed a bug where the ambiguity list behaviour was inconsistent. (Bug #496)
    E.g. A postcode search for 'BS35 2NP' with combined list mode produced an ambiguity list. Select did not work on that ambiguity list.
  3. Fixed a bug where Matchcode 5 uses address formatting settings without checking them (Bug #253)
    E.g. If the ELIMINATE value for Organisation in the waf.ini file was set to a value outside of the allowed range 0-9 the value would have been allowed. Now with this fix all waf options would be set to a default

Release Y08M02

Matchcode UK Engine Version 5.2.7

  1. Fixed a bug where after cross matching 'Hill' selecting from the ambiguity list of towns didn't work.(Bug #473)
    E.g. Perform a cross match with 'Hill' as the only input, select a town and the address elements are not populated (now populates town and county).
  2. Fixed an issue where combined list mode caused RESCODE to be 2 instead of 1. (Bug #417)
    E.g. Perform a browse with the postcode 'PE2 6XU'.

Matchcode UK Engine Version 5.2.6.49

  1. Porting Patches for 64bit platform
    • A matched address was returned instead of an ambiguity list because char data types are unsigned on some platforms
      e.g. grange road surgery, bishopsworth, bristal, bs138ld did not return an ambiguity on such systems
    • FFlag field return value was wrong for some addresses because its defined type changes in 64 bit implementations

Release Y07M11

Matchcode UK Engine Version 5.2.6.48

  1. Fixed a problem with the fix to Bug #446 below. (Bug #526)
    E.g. Lookup postcode "bl2 2lq", select a number range then a number, then focus back to building number and try to select again and you get a blank result.

Matchcode UK Engine Version 5.2.6.47

  1. Resolved an issue where some settings in names.ini were being read incorrectly. (Bug #466)

Release Y07M08

Matchcode UK Engine Version 5.2.6.46

  1. Fixed an issue where an organisation selected from the ambiguity list would not appear in the organisation element when using both PAF and Experian together. (Bug #446)
    E.g. Selecting an ambiguity from a Quick Browse of "Elephantfamily,2 Bloomsbury Place,LONDON" did not return an ORGANISATION.
  2. Fixed an issue where the premise number would not be set after a Quick Browse search. (Bug #436)
    E.g. Quick Browse on "capscan,london" did not return a building number.
  3. Set the address key when choosing an address from a name. (Bug #451)
    E.g. Quick Browse on ENAME="MORGAN, P",ADDR="CR2 7EF" did not return an address key.
  4. Fixed an issue where unrecognised potential vanity localities were not being preserved by the non-paf AddWithin option. (Bug #480)
    E.g. Cross Match ADDR="89 Muswell Hill,Rubbish,london", with AddWithin enabled the text "rubbish" should be preserved in the output address.
    N.B. This problem did not affect the AddPNRLoc option which preserves unmatched text that is actually recognised as a genuine locality that is consistent with the postcode.

Release Y07M05

Matchcode UK Engine Version 5.2.6.45

  1. Scottish flats treated the same in the matching engine as they are in the build. (Bug #339)
    E.g. "Flat 2/1, 34 Finlay Drive, Glasgow, G31 2QU" was incorrectly matching to "Flat 1/1"
  2. Fixed an issue where the engine was unable to get DPS codes when flat number and house number appear on same address line. (Bug #410)
    E.g. "2/2 363 Paisley Road West, Glasgow, Lanarkshire, G51 1LX" was producing an ambiguity list on building number.
  3. Resolved a bug where quick browsing would fail with a memory issue on certain addresses, instead of assuming elements are populated, it now shuffles together any populated elements and uses the lowest as area and highest searchable for the browse. (Bug #258)
    E.g. Quick Browse on "D,Kidderminster,Worcs," (the last comma is important) would cause a crash.
  4. Fixed an issue where certain ambiguities were not appearing correctly. (Bug #375)
    E.g. Quick Browse on "Chichester Crematorium" had stopped producing a match or ambiguity list.
  5. Fixed a bug that caused duplicate information to appear in some crossmatch results. (Bug #330)
    E.g. Crossmatching "61 Ashfield Place, Aberdeen, AB10 6QJ" with AddAbove or AddWithin turned on would produce "61 Ashfield Place, Ashvale Place, Aberdeen, Aberdeenshire, AB106QJ"
  6. Fix to prevent input numbers being added along with the PAF number if it is available. (Bug #397)
    E.g. Searching for "Smalleys Farm, 15 Turf Drove, Turves, Peterborough,PE7 2DJ" would return "Smalleys Farm,15,19 Turf Drove, Turves, Whittlesey, Peterborough, Cambs PE7 2DJ1B"
  7. Fixed a bug where postcode scores were always returned as zero. (Bug #349)
    E.g. "Caravan Club Site, Bourton Rd, Moreton in Marsh, GL56 0BT" had stopped matching.
  8. Fixed a bug where ambiguities were not resolved correctly by name. (Bug #187)
    E.g. Browse on Name: "Watts, Jennifer", Select "Leicester, Leics" from Town Ambiguities, Select "Without Locality" from Localities Ambiguities. It used to produce an ambiguity list on building number even though the is only one Jennifer Watts on the street.
  9. Fixed a bug with single search and combined list mode not returning results correctly. (Bug #358)
    E.g. Using Combined List mode to search for "DA7 5QB" didn't return an ambiguity list.
  10. Checking a postcode is on the PAF (using MCD_PostcodeFormat) only worked down to Outcode level. (Bug #411)
    E.g. AB was considered to be not on the PAF because it is only an area.

Release Y07M02

Matchcode UK Engine Version 5.2.6.44

  1. Fixed an issue with the quick browse by postcode ambiguity list where selecting an item would return no results.
  2. Fixed a buffer overflow in MCD_SingleSearch and MCDN_SingleSearch.

Matchcode UK Engine Version 5.2.6.43

  1. Fixed an issue with MCD_AddNonPAFElements where input used in the matching of an address could be added to output making it appear twice.

Release Y06M11

Matchcode UK Engine Version 5.2.6.42

  1. Combined List Mode.
  2. Removed an array limit to cope with a greater volume of data in business database.

Matchcode UK Engine Version 5.2.6.41

  1. Fix for issue with RCDB path setting on Unix where a directory separator was added to the end of a list file name.

Release Y06M08

Matchcode UK Engine Version 5.2.6.40

  1. Fixes to stop fuzzy postcode matching having a detrimental affect when disabled.

Matchcode UK Engine Version 5.2.6.39

  1. Changed default FUZZYPC parameter to 0.

Matchcode UK Engine Version 5.2.6.38

  1. Fixed a bug where Cross Matching '28 Green Road,hemel' and '28 Green Rd,hemel' return different results with the AdvancedFuzzy parameter enabled.

Matchcode UK Engine Version 5.2.6.37

  1. Improved ambiguity list sorting when entries start with a non alpha-numeric character.

Release Y06M05

Matchcode UK Engine Version 5.2.6.36

  1. Enhanced logging information about PAF and Names files being used. This can be activated by setting the LOGSEVERITY level to 1 (Information).
    E.g Wed May 17 16:19:22 2006,Info,MCD_SMAWFS(),"Loaded PAF File C:\Capscan\Capscan.paf - Creation Date 20-01-2006 (PAFonCD)"
  2. Introduced a check to ensure MSCORE does not go over 100%.
  3. Changes made to the fuzzy postcoding mechanism to only use it with invalid postcodes.
  4. An option has been added to disable fuzzy postcoding altogether. See the description of the FUZZYPC parameter in the Matchcode Configuration section of the bookshelf.
  5. Fix made to code that detects if a potential match is a different postcode area from an input postcode to fix a bug which prevented the flag from being correctly set.
    E.g. The input '47 natal road, london, n11 2hu' would end up ambiguous between N11 and SW16.
  6. Changes made to resolve a bug with PCCHGTYP that caused the flag to be set incorrectly to ‘R’ instead of ‘M’ when a input postcodes is both changed by Royal Mail and wrong for the address.
    E.g. With the input '1,hollybush avenue,newport,cf4 8aq' PCCHGTYP was being set to ‘R’ because Royal Mail change cf4 8aq to cf15 8aq, even though the postcode we correctly match to is NP20 6ES.
  7. The ambiguity list order now ignores anything that is not a letter or number.
  8. A bug that allowed an address to be returned as ambiguous, with a blank ambiguity list.
    E.g. The input '46 FALKLAND ROAD, London' is ambiguous between N8 and NW5 but the ambiguity list was not returned until the user focused on building number type.

Release Y06M02

Matchcode UK Engine Version 5.2.6.35

  1. Bug fixes in Rapid Addressing, which was stopping selecting working following subsequent Cross Matches until you do another Browse.

Matchcode UK Engine Version 5.2.6.34

  1. Memory leak fixes.
  2. Enhanced logging information about RCDB files being used. This can be activated by setting the LOGSEVERITY level to 1 (Information).
    E.g Wed May 17 16:19:22 2006,Info,RCDB_InitTable,"Loaded RCDB file C:\Capscan\lndnout.rcd - Creation Date: 10-12-2003"
  3. Documentation corrected for AKMATCHTOP setting.

Release Y05M11

Matchcode UK Engine Version 5.2.6.33

  1. Bug fix in Cross Matching to check that a temporary string has a null terminator.

Matchcode UK Engine Version 5.2.6.31

  1. Single list address formatting bug fixed.
  2. Fixed a bug in quick browse such that if the query is a sub building no Address Key is output.
  3. Fuzzy postcode matching implemented to correct typographical errors in input postcodes.
  4. Fixed a bug to prevent "South Street" input being treated as a locality suspect when searching for a road suspect.

Release Y05M08

Matchcode UK Engine Version 5.2.6.30

  1. Fixed a bug to prevent MSCORE going over 100% when matching "Flat A,12" to "12A"
  2. Fixed a bug in Old to New postcode lookup which sometimes returned garbage when input postcode was not set.

Release Y05M05

Matchcode UK Engine Version 5.2.6.29

  1. Improved default values for options:
    • Address Formatting option, HYPHENATE
      Old default : 0 = No hyphenation
      New default : 1 = Hyphenate with a dash (-)
    • Cross Matching option, MAXTOWNS
      Old default : 2
      New default : 3
    • Cross Matching option, USEPOSTCODE
      Old default : 0
      New default : 1
    • Cross Matching option, ACCEPTPCCHANGE
      Old default : 0
      New default : 1
    • Cross Matching option, AKMATCHTOP
      Old default : 0
      New default : 1
  2. Make old for new postcode lookup work with postcodes included within address lines used as input to cross matching. Previous only worked with postcodes in the input postcode field.
  3. Fix for Unix platforms so it doesn't matter what case the filenames of the Names database files happen to be in.
  4. Porting patches for 64-bit Big Endian platforms.

Release Y05M02

Matchcode UK Engine Version 5.2.6.27

  1. New logging level
    • New parameter : LOGSEVERITY, read from LOGGING section in mcdparam.ini file.
      See Matchcode Configuration section of bookshelf for more details.
    • Input/Output log severity level (-1) added.
    • Added input and output logging.
  2. Porting patches for 64bit.

Release Y04M11

Matchcode UK Engine Version 5.2.6.25

  1. Fixed problem with renewing expired licences.
  2. Removed reliance on rcdb.lst files on UNIX platforms, i.e. This is now consistent with the Win32 version in that you can either specify a path for RCDB files or a list file.

Release Y04M08

Matchcode UK Engine Version 5.2.6.24

  1. Added support for output of punctuation in formatted address.
  2. Fixed bug that stop town being output when not outputting list.

Matchcode UK Engine Version 5.2.6.21

  1. Added support for output of punctuation in PAF address elements.
    New [output] parameter "Punctuation", enabled by default.

Matchcode UK Engine Version 5.2.6.20

  1. Added support for multiple Names databases (one per PAF).

Release Y04M05

Matchcode UK Engine Version 5.2.6.19

  1. Added support for OSAPR (ADDRESS-POINT) under Unix.
  2. Porting patches for Itanium.
  3. Added support for accessing PAF via memory mapped file (Unix beta only).
  4. Use new "Multiple" Address Formatting module to avoid conflicts when used from different places.

Matchcode UK Engine Version 5.2.6.18

  1. Bug fix to prevent buffer overrun in Name matching module.
  2. Allow entries in Single List to be formatted as 11 PAF Elements.
  3. Bug fix to prevent inconsistency when selecting & focusing following Cross Match.
  4. Bug fix to prevent null pointer bug in RCDB.

Release Y04M02

Matchcode UK Engine Version 5.2.6.17

  1. Fixed util library to handle Spanish characters on Unix.
  2. Minor bug fix in finding towns via outward postcode.
  3. County & London Locality formatting options for addresses in Single List now supported via Address Formatting Configuration file, waf.ini.
  4. When reading .ini files use the default value if failed to open file.

Matchcode UK Engine Version 5.2.6.16

  1. Updates to prevent memory leaks when repeatedly calling MCD_Init(), MCD_Exit().

Matchcode UK Engine Version 5.2.6.15

  1. Postcode formatting options for addresses in Single List now supported via Address Formatting Configuration file, waf.ini.
  2. Bug fix in Address Formatting.
  3. Porting patches.

Release Y03M08

Matchcode UK Engine Version 5.2.6.14

  1. When reading .ini files use the default value if failed to read file.
  2. Improve error logging on database access errors.
  3. MCD_Search() : Trim trailing spaces, and bug fix with uninitialised return status.
  4. Tidied API header files.
  5. Force AddrDesc parameter to true because matching now relies on it.
  6. MCD_Select() : Check for invalid selection.
  7. Various cross matching improvements from comparing with MCD6 : Improved handling of number ranges, localities, overlapping names, and fuzzy compare.
  8. Stop RankDBEqual parameter making a difference with only one database.

Matchcode UK Engine Version 5.2.6.13

  1. Set status to SUCCESS if we match to input postcode before trying next database.
  2. Big endian bug fix.

Matchcode UK Engine Version 5.2.6.12

  1. New function MCD_GetCodeLevel(), i.e. Person level, Household level, or Postcode level.

Release Y03M05

Matchcode UK Engine Version 5.2.6.11

  1. Ignore redundant DOS option : DosUseVmm option MCD_DOUBLE_BUFF
  2. Set NAMESONLY flag automatically depending on search type
  3. Changed default PAF setting to ""
  4. New function MCD_FormatElements()
  5. Fixed problem with default line delimiter in single list mode.

Matchcode UK Engine Version 5.2.6.10

  1. Added support for zipped RCDB files.

Release Y03M02

Matchcode UK Engine Version 5.2.6.9

  1. Fixed a NULL pointer bug.
  2. Changed API header files so that pragma pack(1) is used on Win32 platform only.
  3. Fixed a bug in MCD_SingleSearch() to do with detecting a postcode in the query.
  4. Fix setting of Cross Matching Score so that it doesn't go over 100%.

Matchcode UK Engine Version 5.2.6.8

  1. Don't match to a locality-only address if there is more in the input (Eire).
  2. Fixed a problem where names where being returned if the List parameter was NULL.

Release Y02M11

Matchcode UK Engine Version 5.2.6.7

  1. Fixed a problem where ListMode 2 (and 3) was adding ",," before the address in each row of the ambiguity list even if there is no Names database in use.

Matchcode UK Engine Version 5.2.6.6

  1. Added MCD_SingleSearch() and MCDN_SingleSearch().

Matchcode UK Engine Version 5.2.6.5

  1. Added support for Names with ListMode 2 (and 3).

Extranet C/S Only

Matchcode UK Engine Version 5.2.6.4

  1. Implement optional ambiguity list of addresses.
    New mcdparam options : 
        ;----------------------------------------------------------------------;
    ; [OUTPUT]
    ; Controls behaviour of the output subsystem (list building)
    ;
    ; ListMode    : 0=Output common address elements only (no lists)
    ;               1=Output a list for each address element type (default)
    ;               2=Output a single list with one entry per address
    ;               3=Output both address element lists and address list
    ; EntryFormat : Specifies the name of an address formatting
    ;               configuration to use in formatting the addresses in
    ;               the address list.
    ;----------------------------------------------------------------------;
    [OUTPUT]
    ListMode=3
    EntryFormat=waf.ini
    New API function: 
        pMCD_List CAPAPI MCD_GetAddressList _CAP_ARGS(( void ));

Release Y02M08

Matchcode UK Engine Version 5.2.6.3

  1. Porting patches.

Release Y02M05

Matchcode UK Engine Version 5.2.5AE/5.2.6.2

  1. Log Names filename on fail to open.
  2. Changed default value for ADDRDESC from false to true.
  3. Stopped Names loading defaults repeatedly.
  4. Fixed a bug in parsing input person name where strings weren't terminated properly.
  5. Set destlen for uncompress().
    Only affects builds of names database that includes PURN.
  6. In licence checking log proper Caplock error and possibly system error.
  7. Added pragma pack(1) to API include files.

Version 5.2.5AE

  1. Fixed a bug in where it was sometimes blanking out posttown & county. This happened when the status is insufficient and the List parameter is null and there is more than one possible town.
    e.g. pharmavon,avondale hlth centre,avondale st,bolton,lancs,bl1 4ju

Version 5.2.6.2

  1. Changed default value for CHECKNEWPC from false to true.
  2. Fixed a bug that meant log files where sometimes called "(null)" instead of "capscan.log".

Release Y02M02

Matchcode UK Engine Version 5.2.5AD/5.2.6.1

  1. Allow cross matching to accept a match to locality level if the locality is the top of the address. (really only matters for Eire data).

Release Y01M11

Matchcode UK Engine Version 5.2.5AC/5.2.6

  1. Fixed a bug that caused large number ranges to be incorrectly decompressed such that they became unfeasibly large, e.g. {1,...,65536}.
  2. Don't add PNR locality to the address description if we already have a PAF locality in there. This caused addnonpaf to remove both.
    E.g.
    35 North Bragar
    Sandwick
    ISLE OF LEWIS
    HS2 9
  3. Added a check for end of postcode table to stop infinite loop looking for ZE4.
  4. When adding trash words (e.g. "THE") as if they were matched, set the score to 0.0 instead of 1.0, so they are not treated as matched they are just treated as not unmatched.
  5. Fixed a buffer overflow bug in generating a soundex key from an elector name.
  6. Fixed a bug that sometimes caused focusing to produce an empty result.

Release Y01M08

Matchcode UK Engine Version 5.2.5AB

  1. Fixed a problem in the output of areaing.
  2. Fixed a problem with Quick Browse that was introduced in 5.2.5AA and could caused Matchcode to crash.

Release Y01M05

Matchcode UK Engine Version 5.2.5AA

  1. Fixed a problem where Quick Browse by "All" and by "Postcode" didn't return the correct resutls when the query occurs as both a sub-building and a building number. Examples:
    FLAT 1,W2 1BN
    98,W22QJ
  2. Fixed a bug that matched a number with letter to a number within a range.
    Example:
    98A,W22QJ
  3. Increased the maximum address databases that can be search simultaneously from 5 to 8.
  4. If Quick Browsing by "All" and the input contains a number that starts with a digit and ends with an alphabetic, don't bother to search as building number.
    Examples:
    66A,NW32QT
    6A,N22 6DS

Matchcode UK Engine Version 5.2.5Z

  1. Added support for version 17 address database files (used for Experian business data) where the amount of data for a single street overflows that suppored by the version 16 database format.
  2. Fixed a floating point problemette that resulted in different scores for the same address on Windows and Unix.
  3. Don't look for licence server when network licence is being used on the machine that the licence was created for.

Release Y01M02

Matchcode UK Engine Version 5.2.5Y

  1. Fixed a typo in the Break-to-words routine.
  2. Fixed a problem where pay-per-view usage licences were being overwritten.
  3. In MCD_PostcodeFormat() Removed checking for invalid characters other than those specified by Royal Mail.
    The only Royal Mail rules are the "CIKMOV" ones for incodes, the rest must have been derived by us and are no longer valid.
  4. Minor porting patches to allow consistent compilation across platforms.

Release Y00M08

Matchcode UK Engine Version 5.2.5X

  1. Allow a range separated by quote to be treated as a range.
  2. Set a new insufficiency criteria, namely MSG_NUMUNMCH, that returns insufficient when the input number does not match the output.
    New option to disable this feature, set using a new bit MCD_DIFF_NUM_OK in FuzzyLevel.
    e.g. Westminster City Council
    Westminster City Hall
    64 Victoria Street
    London SW1E 6QP
  3. Added a check to make sure that a building number doesn't overflow a short.
  4. Fixed a problem where browsing was matching SW1 to SW1X and SW19.
    A new postcode comparison was introduced.
    e.g. Wilton Crescent,SW1 (Also try SW & SW19)
    Took the opportunity to tidy up and consolidate some postcode comparison stuff.
  5. Advanced Fuzzy was a little over-zealous in matching names contains words with a very high word weight (i.e. low occurance in the database), which had too great an effect on the percentage of the total match.
    e.g. Doncaster Careers Office ---> Used to match ---> Doncaster Mancap
    24 Thorne Road
    Doncaster South Yorkshire
    DN1 2DH
  6. OS/390 porting patches.
  7. A typo in the code for parsing the MCDPARAM.INI configuration file was looking for "FLAGPNRLOG" instead of "FLAGPNRLOC"

Release Y00M02

Matchcode UK Engine Version 5.2.5W

  1. Endian & RISC alignment bug.
  2. Added check for preprocessor symbol 'sinix' to top of platform.h; this symbol is defined automatically by the C/C++ compiler on SINIX.
  3. Increased the amount of address data support by MEF files.
  4. Fixed EBCDIC bugs caused by replacing home grown itoa() with sprintf().

Matchcode UK Engine Version 5.2.5V

  1. Fixed bug in the routine to load the Names configuration file, where it set the file handle to NULL instead of testing it.
  2. Added support for 30 day trial licence.

Matchcode UK Engine Version 5.2.5T

  1. In mcdparam.h
    Made MCD_DEF_FUZZY include MCD_CHCK_NEWPC since this never used to be optional.
  2. Fixed a problem with Address Key Lookup with using address keys from business.paf.
  3. Fixed a data overrun bug in parsing input Elector Name.
  4. The 5.2.5R changes to Quick Browse disappeared. Now put back in - MCD_Search() now checks user.txt first. If not in there, it will work as before.
  5. General tidy up. Removed redundant file IO code. Fixed a lot of compiler warnings - unreferenced variables, signed/unsigned mismatches etc.
  6. Fixed it so that a complete range in the input will be compared with both and odd range and an even range on the PAF.

Release Y99M11

Matchcode UK Engine Version 5.2.5S

  1. Introduction of new porting layer for file I/O.
  2. Rewritten MCD_ReadIni() to use GetPrivateProfileString() now we have a version of it for non-Windows platforms.
  3. Don't fuzzy match words less than 3 characters in length.
  4. Reduce score for a fuzzy matched building name that doesn't go to the start of the line.
  5. Fix bug where the setting of MCD_CHCK_NEWPC in MCD_Param.FuzzyLevel was ignored.
  6. Clear RCDB_Path if it is garbage, and don't register the facility until a path has been found.

Matchcode UK Engine Version 5.2.5R

  1. Conditional compilation to support Electoral Roll database with/without personkey data. New ZLIB library version 1.1.3
  2. Quick Browse now checks user.txt first. If not in there, it will work as before.
  3. Further MVS porting patches.
  4. Fixed problem in spotting BFPO addresses.

Matchcode UK Engine Version 5.2.5P

  1. Fixed potential RISC bug.
  2. Support for new Names table format (elect.db version 2). This includes a Capscan derived Person Key for linking external data to person level. Person Key is not valid across editions of the database.
    New API routine (mcdnapi.h) :
    int NAM_GetPersonKey(pNAM_List NameList, unsigned long *PersonKey)
  3. Patch in MCD_Matchcode() so that Town & County are returned for insufficient matches even when Lists are not being built.
  4. Patch to MCD_PostcodeFormat() to accept W in the third character position for new outcodes E1W.
  5. MVS porting patches.

Matchcode UK Engine Version 5.2.5O

  1. Fixed problem browsing "beech house,SN8 3SD".

Matchcode UK Engine Version 5.2.5N

  1. In MCD_AddNonPAF(), change to stop trying to add unmatched postcodes to PAF addresses.
  2. Added support for MEF for street names that are the same in standard form but different in original form.

Release Y99M08

Matchcode UK Engine Version 5.2.5M

  1. Fixed bug that caused crashes when running on big-endian machines like the Sun SPARC and HP PA-RISC.
  2. Added a test to check for BFPO in the input when checking for foreign. If text found, we return foreign with ZZ999WZ as Postcode.
  3. Fixed a problem where MCDN_SetFocus() returned MCD_NOHITS. Now only returns MCD_SUCCESS or MCD_ERROR.
  4. Fixed a problem where building name + pnr locality returned success. Now we consider pnr as a weak match and therefore conflicting.
    e.g The Wheelhouse,Shotatton,Shrewsbury,Shropshire,SY4 1JG
    was matching to:
    Wheelhouse,Shrawardine,Shrewsbury,Shropshire,SY4 1AH

Matchcode UK Engine Version 5.2.5L

  1. Patch to handle overflowing MEF tables.

Matchcode UK Engine Version 5.2.5K

  1. Fixed Linux compilation problem that caused MCD_Extract() to be left out of the resulting Matchcode binaries.
  2. RCDB_Init(): Fix bug where allocated resources are not freed on premature exit, by calling RCDB_Exit() before returning error status.
  3. VMS Porting patches.
    • Don't include <dos.h>, <io.h>, <conio.h> or <malloc.h> if VAX defined.
    • Define __min as a macro if MIN_UNDEFINED is defined.
    • RCDB_Init(): Replace reference to _strupr() with strupr().
    • Don't bother looking for backslashes in RCDBPath if VAX is defined.
    • Add implementation of strupr() and strncasecmp().
    • Change strcasecmp() so it does not alter the strings.

Matchcode UK Engine Version 5.2.5J

  1. Bug fix in RCDB_Init().
    Was copying garbage from nFindBuf.name when no RCD files were found.

Matchcode UK Engine Version 5.2.5I

  1. New Quick Browse : MCD_Search() by ALL
  2. Quick Browse problems:
    Fixed a problem with Quick Browse where the number from the query was cleared and therefore selecting a street would give an ambiguity of numbers.
    e.g. 16 princes gate,SW7

    Fixed a problem where query was cleared.
    e.g. sar,basingstoke

    Also fixed a problem where a search by 'A' did not work when there was a space within pc+dps.
    e.g sw1a 1aa1a did not work but sw1a1aa1a did.
    Fixed a bug for an address search by 'C' so that it would work for even a character used for company name.
    e.g. B,W1A 1AA

    Also for an 'A' search, if the input has no comma and can be at least an outcode, a postcode search is applied.
    e.g. E8 1AD
    Fixed a bug for new search by 'A' where the input without comma was wrongly placed in the postcode as well as the other address elements.
    e.g.
    Kentish
    High Street
    Station
  3. Fixed a bug in MCD_Select() where following a Cross-Match a Select and Deselect combination would widen the result set.
    e.g. 11 Priory Road, Bristol, BS18 2BX
    The result of a cross-match will now be exactly the same after a select followed by a deselect.

Release Y99M05

Matchcode UK Engine Version 5.2.5H

N.B. mistakenly released as 5.2.5H again
  1. Fixed a problem in MCD_PostcodeFormat(), when the CHECK_EXISTS option was specified the return status of the database lookup wasn't being tested properly.
  2. New API function : MCD_GetVersion(). Returns the API version number.
  3. Changed the sufficiency check for wrong postcode area to only relate to London.
    e.g. 100 Hills Road,Cambridge,NW3 2QW
    will not complain about Wrong Area any more.

Release Y99M02

Matchcode UK Engine Version 5.2.5H

  1. Bug fix in MCD_AddNonPAF(), changed "=" to "==".
  2. Fixed a bug where "N2" matched "N20" and "N" matched "NW". For the outcode, trailing spaces were added to make a length of 4 chars. For one-char areacode, we allow the following character only to be a digit.
    e.g. Browse HIGH ROAD,N2 (or N)
  3. Added non-WINDOWS prototypes for MCD_MBAGWRFSLDS() to mcd_api.h
    It was in 5.2.4 but not 5.2.5
  4. Fixed a bug when the search results were being discarded the output PAF address was not always being cleared.
  5. Use old to new postcode lookup when doing Quick Browse by Postcode.
  6. Added a flag to be set when there are no names on electoral roll. This flag can only be used when a full address is resulted. To retrieve this flag MCD_NamFlag, use MCD_GetNameFlag().
  7. Fixed a problem where an Organisation matched successfully to a PO BOX, even if the PO BOX was not in the input. Now we set status to insufficient.
    e.g. BOYTON FINANCIAL SERVICES LIMITED,HALSTEAD,,,, Paf 3/1998
  8. Fixed a bug where Cross Matching was reporting WrongArea when the input PC had an incorrect outcode.
    e.g. 49 Park End Road,Romford,Essex,RN1 4AX

Release Y98M11

There is a major release of Windows Matchcode (version 5.2.5) on this quarters CD with many enhancements over version 5.2.4:

PAF Location

The main difference between versions 5.2.5 and 5.2.4 is the ability to search across multiple databases. This is essential for Matchcode Commercial in which you need to be able to search the database of Royal Mail PAF addresses (Capscan.PAF) and the database of Business addresses (Business.PAF).

When specifying the PAF Database Location (either by the CD environment variable, or via the MCD_SetPAFName() function) it is now possible to specify multiple database names separated by semicolon ';'.

Preference

The order that the database names are entered is the order in which they are searched.   By default, Cross Matching will stop searching at the first database where it finds a successful unambiguous match.   This avoids ambiguities where the same address appears in more than one of the databases being searched.   For this reason you should enter your preferred database first.

There is a new option (set via the function MCD_SetRankDbEqual()).   If set this to true Cross Matching will no longer stop at the first database where it finds a match, and instead return matches from all databases.

N.B. We recommend that Matchcode Commercial users list Capscan.PAF before Business.PAF to avoid mismatches where there is only one organisation on a street.

Using both Names & Commercial

Since the names database files are closely linked with a specific address database, the Names Database paths also accept multiple database names separated by semicolons.

The order that the databases are listed in the Names Database paths is parallel to the address database names listed in the PAF Database Location.   Even if an address database does not have an associated names database a semicolon must be entered here.

For example, if your order of preference is Royal Mail data, Business data, you set the paths as follows :

MCD_SetPAFName("D:\Capscan.PAF;D:\Business.PAF");
NAM_SetNDBPath("D:\Elect.DB;");
NAM_SetBDBPath("D:\NamesIdx.DB;");

Or, if your order of preference is Business data, Royal Mail data, you should set the paths as follows:

MCD_SetPAFName("D:\Business.PAF;D:\Capscan.PAF");
NAM_SetNDBPath(";D:\Elect.DB");
NAM_SetBDBPath(";D:\NamesIdx.DB");

Release Y98M11

Matchcode UK Engine Version 5.2.5F

  1. Fixed a bug where the old to new postcode lookup was shutting down RCDB. Added reference counting so RCDB_Init() and RCDB_Exit() calls can be nested.
  2. Fixed a bug where a locality match in one postcode was carried forward to the next postcode.

Matchcode UK Engine Version 5.2.5E

  1. Fixed a bug where a Postcode Access for a postcode with different town to the input crashed the program.
    Example:
       TAYLOR WOODROW CONSTRUCTION LIMITED
   SOUTH TERMINAL PROJECT OFFICE
   JUBILEE HOUSE
   GATWICK AIRPORT
   CRAWLEY
   WEST SUSSEX RH6 0NP

Matchcode UK Engine Version 5.2.5

  1. Added a new exported function MCD_TimeToGo() that returns the number of days left on a date-restricted licence
  2. Added a feature to make locality browsing work for PNR (postally not required) localities.
  3. Added option to prefer Paf databases by the order they are listed.
    This includes the following:
    1. A flag MCD_RankDbEqual is used with a default value of 0: This means "stop at first successful match (with pc+dps)".
    2. To set or unset the above flag, call MCD_SetRankDbEqual(char Value) where Value is 0 or 1.
    3. If flag cleared, the order of preference will be in the same order as the Paf names in the string, e.g. : "D:\Business.paf;D:\capscan.paf" means prefer Business first.
  4. Fixed a bug where a double-barrelled forename could not be selected after a browse.
    e.g. JONES browsed in CARDIFF and then EMMA JAYNE selected.
  5. Fixed a bug where a double-barrelled forename could not be browsed.
    e.g. JONES,EMMA-JAYNE browsed in CARDIFF.
  6. Made a change so that a FLAT cannot be fuzzy-matched any more.
    e.g. Sheridan,Unit M1,Chelsea Garden Market,Chelsea Harbour,London,SW10 0XE
  7. Stopped treating memory array overflows as errors, instead just fails. This happens by design when fuzzy access finds two many options, and was never intended to be logged as errors.
    e.g. Sheridan,Unit M1,Chelsea Garden Market,Chelsea Harbour,London,SW10 0XE

SDK CD 1.4 Y98M08

There is a minor release of Windows Matchcode on this quarters CD, changes include:

Postcode Changes

Matchcode will now recognise old postcodes and automatically replace them with the new postcodes.  This is done at the beginning of all search routines that can take a postcode as part, or all, of the input query.  In the case of Cross-Matching having the input postcode updated helps to confirm the correct match and reduce the number of records rejected by the "don’t accept postcode change" option.  In the case of Rapid Address updating the postcode may be the sole objective - particularly with a Rapid Address type batch job.

The old postcodes are recognised by using a table of postcode changes, PCCHANGE.RCD.  To make this table available to Matchcode it must be in the path specified in a call to RCDB_SetRCDBPath().

The data from PCCHANGE.RCD is indexed on postcode like other RCDB files, but is used internally by Matchcode to update old postcodes.

For an example, try Rapid Addressing with AB1 2AA.

Release Y98M08

Matchcode UK Engine Version 5.2.4J

  1. Fixed another problem that caused different results when Query parameter is NULL
    e.g. "newhay court, empsons hill, dawlish, devon, ex7 9bq"
    "hartlake roundalls,golden green"

Matchcode UK Engine Version 5.2.4I

  1. Fixed problem that caused different results when Query parameter is NULL
    e.g. "halls hill, stone st sev kent"
    "the hartlake lane,hartlake roundalls,golden green" "the oast,stevens farm,hawkhurst kent"
  2. Allow a number range to be separated by :
    '.',',','-','/'
    This complements a change in break-to-words which hasn't been implemented yet, 'cos it needs further testing.
  3. A much simplified implementation of using PCCHANGE.RCD.

Matchcode UK Engine Version 5.2.4H

  1. Added a new feature to use PCCHANGE.RCD.
  2. If there is a gap between a Flat name and the street, we do not add to the score. But now we only add the position to the Address Description so that the Flat does not get added as a NonPaf element too (no duplications).

SDK CD 1.3 Y98M05

There is a minor release of Windows Matchcode on this quarters CD, changes include:

Pay Per View RCDB

This version of Matchcode is required to allow access to those RCDB files where access to the data is charged per lookup, e.g. Mosaics from Experian. These additional datasets are not supplied on the PAF CD, but are available on request from Capscan.

New option for specifying the location of RCDB files

Previously, through RCDB_SetRCDBPath(), you could only specify a single directory for RCDB files. This was restrictive in the sense that all the files had to be in the same folder and all the files in the folder specified would be accessed even if they were not needed.  Accessing more RCDB files than you need slows down a search.

As an alternative to specifying a folder, you can now specify the name of a list file (which must have a .LST file extension).   This is simply a text file that contains a list of all the RCDB file names.  This allows you to, for example, copy the smaller RCDB file to your local hard disk (for speed of access) but leave the larger Postzone file on the CD.   To do this you would create a list file that looks something like this:

D:\PZONE.RCD
C:\MYRCDB\CONSCODE.RCD
C:\MYRCDB\CONSNAME.RCD
C:\MYRCDB\DHANAME.RCD
C:\MYRCDB\DISTCNTY.RCD
C:\MYRCDB\WARDNAME.RCD

Release Y98M05

Matchcode UK Engine Version 5.2.4G

  1. In Address Key lookup a millennium compliance patch. DOH!
  2. Fixed a bug in fuzzy compare where some good matches were ignored.
  3. Search in all towns that have an equivalent score.
  4. Score a street with a matching number higher than a street without a matched number.
  5. Fixed a bug that caused Address Improvement mode to trash the Address Description, and hence cause MCD_AddNonPAF() to return MCD_NONPAF_FAIL when nothing added at all.
  6. When doing Address Search by 'P', the unsearchable queries such as a FLAT or a number with an alphabetic part are searched separately in Building Name & SubBuilding Name without "*" added to them.
  7. A new function MCD_GetCrossMatchScore() was added.
  8. A bug was fixed where a town was fuzzy matched when there was an outcode present.
  9. RCDB changes:
    1. Added a security check for the licensing of RCDB data.
    2. The RCDB_Path can also hold the filespec for an INI file that lists the RCDB files to use. NOTE: The name of the INI file has to be included in the Path.
    3. If RCDB_InitTable fails for any reason, before returning 0, the function cleans up after itself.
  10. Fixed a problem with the way the Address Key index was used that could cause Address Key lookup to fail.

SDK CD 1.2 Y98M02

Security

Matchcode no longer uses dongle (hardware security key) for copy protection.  This release of Matchcode uses a new copy protection system, which means that the software must be registered on each machine that it is to be used on.

Registration

To register the software on a machine, after installing you must run the Product Registration program and contact the Capscan Sales Dept (020 7267 7055) for a User Key.

Alternatively you can register via e-mail to Sales@Capscan.co.uk.  Run the Registration Program to obtain your Registration Key, and send an e-mail to Sales@Capscan.co.uk with "Matchcode Registration" as the subject. The message should include your Registration Key, User Name, and Company Name.  You will receive a reply containing your User Key, which you can then cut & paste to the Registration Program.

Fuzzy Matching Options (Cross Matching)

New settings that allows certain number matching options to be disabled.  These include:

  • Match 1 to 1A
  • Match 1A to 1B
  • Match 1 to 1-3 (i.e. number within range)

These options are enabled by default, but can be turned off via the new options.  All of these types of "fuzzy" number match would be given a lower score than an exact match, so should an exact match be found it would be preferred.   It is useful to have these features enabled in an interactive session, so that the "close" matches will be displayed, but it is better to disable them in an automatic batch job to avoid incorrect matches.

Release Y98M02

Matchcode UK Engine Version 5.2.4

  1. A fuzzy name i.e. organisation or building with a wrong building number is now considered to be insufficient.
  2. A facility manager was added for use by the Matchcode internal systems. PAF is registered as one facility, with Names and RCDB as separate facilities so that they can be opened and closed independent of each other & the PAF. This also introduces a new error system to simplify any future addition of new errors codes/messages.
  3. Fixed a memory leak in the list building output system.
  4. Fixed a bug where a locality & county were being matched to overlapping portions of the input address.
  5. MCD_PostcodeFormat(), the input postcode can now be checked for invalid chars i.e. everything except alpha, digit and space. Giving a new return status of MCD_PF_BAD_CHAR.
© Capscan Limited 2011. All rights reserved