================================================================== M$ Access tables for SSS database format under the new Sim system ================================================================== For 7 days racing week week ending Sunday nights, week-numbered as under the old SIM naming system. ========================================================== ========================================================== [NB: Scroll down to '1) WHAT'S INCLUDED' to find start of text on how to use the SSS Update files] ========================================================== ========================================================== !!!! ------ !!!! ------- NOTES -------- !!!! ------ !!!! w/e 8202 (Jan 3rd 2021) revised at Jan 8th ------------------------------------------ (See also Appendix 1 and the previous post below this one) I have revised my [tblhorsedata] [hid_short] field modification for w/e 8202 and have issued a replacement SSS import file for the week. The revision is that the [hid_short] modification will now apply ONLY to horse IDs greater than 12200000000 (ie: year 2021+ 2yo-bred). Thus all previously bred horses, and this year's 3yo breeds, will maintain their previous method of ID modification for listing in the SSS v4.33 front-end. Please refer to section 2(c) in the 'WHAT'S INCLUDED' part of these NOTES regarding the use of [hid_short]. So -- i) All horse IDs less than 12200000000 have the leading '1' removed for the [hid_short] SSS version: eg: new Sim ID 11200000001 SSS version 1200000001 ii) From w/e 8202 (Sun Jan 3rd 2021) horse IDs greater than 12200000000 have both their leading '1' removed, and also their 4th digit, which is zero: eg: new Sim ID 12200000001 SSS version 220000001 This is because the data-type in the SSS is otherwise broken with the new 2yo IDs commencing with 122. (The number is otherwise too big). If you updated an SSS_v4.33-compatible database with the version-1 [8202_SSSdata.mdb] file, non-2yo horses will have had their ID value for the week compacted by the removal of an internal zero. This was my original (rushed) design decision as was required for the new 2yo [hid_short] values, to deal with them exceeding the SSS_v4.33-compatible maximum, and which will be required for all ongoing years, but which I applied to all horse IDs for the week's file. In retrospect, applying the same ID compaction to previous year's breeds, and to 2021 3yo breeds, does not make sense as it removes consistency in the ID numbering. Version-2 of the [8202_SSSdata.mdb] update file therefore only applies the necessary ID compaction to current 2yos, and to future 2022 breeds. If you updated an SSS_v4.33-compatible database with the version-1 file, you can revert the non-2yo IDs for w-e 8202 to their previously compatible values by running the version-2-included Query:[update wk 8202 hid_short values], which updates the requisite 22750 records. ----------------------- w/e 8202 (Jan 3rd 2021) ----------------------- (See also Appendix 1) The horses in my [tblhorsedata] [hid_short] field still carry the old Sim ID if they were in the 5156 breeding file, otherwise their ID is offered in a modified version to enable use of the files in the existing SSS version 4.33 a) Up to w/e 8195 (Sun Dec 27th 2020) horse IDs have their leading '1' removed: eg: new Sim ID 11200000001 SSS version 1200000001 b) From w/e 8202 (Sun Jan 3rd 2021) horse IDs have their leading '1' removed, and also their 4th digit, which is zero: eg: new Sim ID 12200000001 SSS version 220000001 This is because the data-type in the SSS is otherwise broken with the new 2yo IDs commencing with 122. (The number is otherwise too big). ------------------------ w/e 7691 (Aug 11th 2019) ------------------------ New field [raceid] in [D_tblraces] ---------------------------------- I am including a new field [raceid] in the [D_tblraces] table from this week. This will allow easy weekly linking of old-style quoted raceNumbers (racenums) to the actual SIM pages for results or viewer links. Field structure is: ------------------ [raceid] Data Type: Number Field Size: Long Integer Dec Places: 0 Required: No Indexed: No ------------------------ w/e 6998 (Sep 17th 2017) ------------------------ Ongoing correction for non-standard owner name contractions ----------------------------------------------------------- I realised a while back that, although the weekly file contains the up-to-date owner name contraction tables (for longer owner names used in databases with shorter owner name fields), I have never actually transferred non-standard contractions (ie: those that do not have the underscore as the 4th character from the right) to the [D_PRE_tblhorsedata] tables. This only affects 5 of the 12-character owner names and 16 of the 10-character names, as you can see from the file in the weekly Update Packs. From this week's update, that error is corrected, and I will add the compilation of a correction file for all previous results to my list of stuff I really hope to get round to sometime !!! ------------------------ w/e 6795 (Feb 26th 2017) ------------------------ After having actually used last week's file for a local-race query (see previous note w/e 6760 below), I have decided to change the field's formatting. When I instigated the new [loc_etc] field in [D_tblraces] field in w/e 6760, I set it as a text field with unwritten fields being 'Null' by default [Not required]. As of this week (6795) I have made it a [Required] field and set the default (ie: non-local-race) string value to '-' which makes results filtering much easier. I have reworked all the 6760-6788 files on the server to this new format so, if it's relevant to you, you can delete the previous updates and download and import the new ones. Or, if required, you could instigate your own updates for weeks 6760-6788 based on this data:- Table design: field [loc_etc] ----------------------------- Original: Data Type: Text Default value: [none] Required: No Allow Zero Length: No New from w/e 6795: Data Type: Text Default value: "-" Required: Yes Allow Zero Length: No ------------------------ w/e 6760 (Jan 22nd 2017) ------------------------ i) I am including a new field [loc_etc] in the D_tblraces from this week. This is a single-character text field where the figure "1" indicates a local-race. I have asked Mike if he could introduce an indication of owner restricted racetypes in his supplied data, which he has said will turn his attention to as soon as he can. Once he has addressed it, indication of owner restricted races will also subsequently be given in this new [loc_etc] field. ii) There is a new track Perth (ID 96 - PTH) in the Australian region. If you still use the SSS interface, you'll want to add the track under the Utilities menu option. ------------------------ w/e 6578 (Jul 24th 2016) ------------------------ Gelding came in this week, albeit only on Sunday July 24th, the last day of the weekly update. I'm not sure if it might become necessary to know whether a horse has been gelded or not from a stats point of view but, just in case, the weekly update files are now being checked for this. The [sex] field in the table [D_PRE_tblhorsedata] will show sex "G" rather than "M" for races run by male horses subsequent to their declared gelding time, if applicable. ------------------------ w/e 6242 (Aug 23rd 2015) ------------------------ More on name changing -- see preceding note (w/e 6025) -- Mike started releasing daily horse name change data four weeks ago and I am incorporating the ongoing name changes into the weekly SSS update files as of this week. This means there is still a need to correct name-changed horses that are in the database from the last 7 months, and I will issue update files to deal with this as soon as I can. The last 3 weeks will be fairly straight- forward, as the individual week files are directly available, but the rest will be a little more complicated -- I'll let you know !! On a related issue, it recently became apparent that only 2yo name changes were being swept into the race files that drive the viewers. An example of this can be seen at derbyfever.com/onerace.asp?whicher=old&raceid=1516630 where first-time-out 3yo BEAU CONNECTION is listed correctly on the card, but runs in the viewers under her birthname NIGHTTIME RAINBOW. This has now been corrected for future races, but it seems likely that the back- files will stay as they are. There will no doubt be a fair few of these instances out there. ------------------------ w/e 6025 (Jan 18th 2015) ------------------------ The inclusion this last week of the option to rename horses prior to running them means that it is quite possible that names of new-breeds in this and subsequent SSS updates will not match the final running name of the horse. Specifically, new-breed data is released each day at 8am gametime. Each record (by ID number) includes the horse name current at that time. If a horse is given its final running name before the 8am following its creation, then all will be well. But if its name is changed after that first 8am cut off, it will not be relisted and there is currently no way to determine its changed name. Once a horse runs, its name will become fixed, of course. Mike has said he will attend to a new data source to address this issue, as well as a 'catch-up file' for the intervening period, but until he does please be aware of this possibility. ------------------------ w/e 5773 (May 11th 2014) ------------------------ I am including a new field [sex] in the D_tblhorsedata from this week, giving the sex of each running horse. ----------------------- w/e 5703 (Mar 2nd 2014) ----------------------- For the first time, there was a name-clash (duplicate) on the 12- and 10- character owner name contractions this week. I have manually amended these contractions as shown below, with the thinking that later names such as silversun10epic1 might arise. existing18(14) [oname_15] [oname_12] [oname_10] ---------------------------------------------------------------------- silversunepic1 silversunepic1 silversu_ic1 silver_ic1 5703name18 (15) --------------- silversun9epic1 silversun9epic1 silversu_ic1 silver_ic1 manually amended to >>>>>>>>>> sil_un9epic1 sil_9epic1 <<<<< THESE USED Further such instances will be noted in a text file in the weekly update zip. ----------------------- w/e 5612 (Dec 1st 2013) ----------------------- Two new problems have come to light this week. i) More than 99 races at a track ----------------------------- Track 09 NJ ran 107 races on Sat 30th Nov (wk5611) and this means that the SSS v4.33 display has finally had to be broken. I have assigned the 107 races racenums 5611.09001 to 5611.09107, which run numerically backwards in line with the Sim's Race Results Displays (ie: race 09107 is the first to be displayed in the online Sim results as it is the 'latest result' of the day, and 09001 is the last result on the final page of those results, as it was the first posted.) Although these numbers do not display correctly in the SSS interface (as you can imagine), they work fine with Access as long as you set any racenum field properties to Format: General Number Decimal Places: Auto If you run any queries against a racenum field, just ensure you have taken into account the potential different format. I am starting a list of Race Days & Tracks where this applies. Hopefully it was a carding glitch and won't occur again - the most races that usually run on a day at a particular track is around 50. ii) Owner names longer than 15 characters ------------------------------------- By chance I also noticed when investigating the above that there are now a number of stablenames of 16 and 17 character length that have crept in. Although a stablegroup cannot be named with more than 15 characters, it appears that additional stables to such a stablegroup are automatically offered supplementary incremental digits at the end. Thus I discovered the stablename eddiejrcolongon25 (17 characters). The ramifications of this are that: a) I have increased the size of the stablename/ownername field [oname] to 18 (- hopefully noone is going to make more than 1000 stables in a group with the same base name !!) b) Substitute contracted versions of each name are provided in alternative fields in the [tblraces] file, as previously: onname = maxlength 18 chars oname_15 = new contracted 15 char oname version oname_12 = new contracted 12 char oname version oname_10 = new contracted 10 char oname version You will need to use the particular version you work with. In all cases, the final 3 chars of the stablename are retained. See Section 2d) and Appendix 3) of this document for more details. c) Owner names affected prior to this new 18 character fieldlength will have had all their races recorded under the same (initial 15 characters) but, after further investigation, only three stablegroups appear to have been affected. Two of these (jessicamichelle and kevincarolynhaw) seem to have ceased playing and only one race between them is affected. The other group (eddiejrcolongon) has 1114 affected races, and I will hopefully be able to issue an update at a later time (although things like this seem to get put on the backburner, I must admit !) ------------------------ w/e 5178 (Sep 23rd 2012) ------------------------ I discovered this week that that owner names can in fact now be up to 15 characters long - not 12 as I had previously understood. At the time of writing, 15 character names have only been implemented for New Stablegroup signups. Signups for New Substables are set at 12 characters maximum. Mike has said it was his intention that all signups should be potentially up to 15 characters long in the new Sim, and the matter should be corrected for substables at some point soon. This has meant have had to revise my treatment of the longer owner names. See section (2d) regarding this. I will issue an update method for previous append files w/e 5164 & 5171 as soon as possible. Ongoing apologies for the delay on this. !!!! ------ !!!! ------- !!!! ------- !!!! ------ !!!! ========================================================== ========================================================== PLEASE READ BEFORE PROCEEDING TO USE THESE TABLES 1) WHAT'S INCLUDED ------------------ a) Included are the two database tables [tblraces] and [tblhorsedata]. They are prefixed D_ and D_PRE_ respectively. These tables contain the data to append to an existing SSS database, which data follow directly on from the previous raceout update tables I have made, and retain the old Sim naming system for days (weeks), tracks and races. The tables are in Access97 format, and so should be recognised by all Access versions other than to Access2013. You will need to tailor the [D_PRE_tblhorsedata] to your personal requirement, (hence the 'PRE' prefix), so please READ ON !! b) Also included are the necessary Append queries and SQL text versions of these, just in case you mess up the graphical ones !! c) Included in the database are tables: [ALL_owner12_swapTable_5164-5171] - name swaps implemented weeks 5164-71 [ALL_owner15_swapTable] - name swaps implemented w/e 5178 on (see secn 2d below). 2) TABLE FORMAT --------------- a) [D_tblraces] is exactly the same as the current SSS format table. b) [D_PRE_tblhorsedata] contains three extra alternate fields - one alternate horse ID field, one alternate owner name field and a BPs field. In each of the first two cases (horse ID and owner name), you must choose which version to retain, depending on how you want to configure your tables for the new Sim. You should delete the unwanted field from each pair and rename the remaining field, if necessary, before you make the append (see [c & d] below for the detail). From w/e 5479 the BPs column is included, showing the BPs earned in each race. You can use this as you see fit. c) Alternate horse ID fields [hid], [hid_short] -------------------------------------------- (Revised & corrected Oct 22nd 2012) Horse IDs have been changed in the new Sim and are now 10- or 11-digits long. These new IDs are applied to all SIM horses past, present and future and stay with the horse for all time, whether retired or still racing. This length/size of ID is too large for the original SSS 'Long Integer' datatype. The rightmost 8 digits of the new horse ID denote its serial breeding position in a year (ie: 1st breed of a year is [x]xx00000001) and the leftmost 2 or 3 digits - [x]xx - indicate the year of birth; or, to hopefully make it easier to relate to, the calendar year the horse is/was 3yo. (See Appendix 1). So: currently bred horses (in 2012 AD) have an 11-digit ID, of which the leftmost three digits are 112 if currently a 3yo, and 113 if currently a 2yo. In order to accommodate new horses into the existing SSS v4.33 I have optionally reduced the numerical length of the new horse IDs. All horses that were current in the horse pool (breeding file) at the end of the OldSim (week 5156) still retain their old ID in my [D_PRE_tblhorsedata], allowing back-referencing for statistical purposes, which is vital. But for new breeds under the new Sim system, I have optionally removed the leftmost 1 (of the 11 digits) to retain a 9- or 10-digit ID, which still then fits into the original SSS field (so I can then provide a raceout for current SSS users before a new SSS is made available). This option is provided in the field [hid_short]. The modification only (mainly) affects horse IDs for those horses bred into the new Sim current racing pool (ie: 2yos and 3yos) and therefore is quite safe to use. Your options re horse ID field ------------------------------ i) If you want to directly use the new long Sim IDs for new horses in your database, you will first need to change the field datatype for [hid] in your SSS database to 'double'. This may be easy or not, depending on your computing power. If you go this route, you will then need to delete the field [hid_short] in my [D_PRE_tblhorsedata] before appending the table. ii) I have decided to use the shorter version of the [hid] in my own SSS database, and this will be the version I will include in the raceouts I will produce - certainly until the new SSS is finished. If you go this route, you will need to delete the field [hid] in my [D_PRE_tblhorsedata] and rename the field [hid_short] to [hid] before appending the table. d) Alternate owner name fields [oname], [oname_15], [oname_12], [oname_10] ----------------------------------------------------------------------- Owner names in the OldSim were limited to 10 characters in length. In the new Sim they may now be up to 15 characters. For the first 2 weeks of creating these Append files I understood the maximum name length to be 12 characters. In order to accommodate the new longer character names into the existing SSS v4.33, I have modified those that have so far appeared by retaining a bulk of the leading characters of each name and a small group of the final characters of the name, separated by an underscore. For the first 2 weeks of the Append files, while I was under the impression that the maximum name length was 12 chars, I used 2 final characters for the contracted names. From the third week's file (5178), I have revised the contraction method to incorporate the final 3 characters of the original name. Not only do I now consider the 3-character end group will be less likely to produce 'conflicting' names, but it will be a clear indication of whether a contracted name has been updated. I still hope to find the time to issue an updater for the first 2 weeks. In the [tblhorsedata], three owner fields were given (prior to Dec 1st 2013): [oname] = full name, up to 15 characters [oname_12] = name up to 12 characters, contracted as necessary [oname_10] = name up to 10 characters, contracted as necessary Details and examples of name contractions are given in Appendix 3. !!! - [section update Dec 1st 2013] - !!! ----------------------------------------- 17 character owner names have now been discovered. - see Notes 'w/e 5612 (Dec 1st 2013)' at the Head of this document. a In the [tblhorsedata], four owner fields are now given: [oname] = full name, up to 18 characters [oname_15] = name up to 15 characters, contracted as necessary [oname_12] = name up to 12 characters, contracted as necessary [oname_10] = name up to 10 characters, contracted as necessary Details and examples of name contractions are given in Appendix 3. Your options re owner names --------------------------- i) If you want to use the new longer-character-maximum owner names in your database, you will first need to increase the field length for [oname] in your SSS database to 15 or 12. This may be easy or not, depending on your computing power. However you proceed, you will need to delete the unwanted name fields in my [D_PRE_tblhorsedata] and rename the remaining field [oname] before appending the table. ii) I originally decided to use the 12-character version of the [oname] in my own SSS database, and am going to continue with this version for the time being. The version I will include in the raceouts I will eventually produce (for import to SSS 4.33 via its own import routine) will be the modified 10-character version, until the new SSS is finished. 3) APPENDING THE TABLES ----------------------- When you have decided which 'horse ID' and 'owner name' versions you want to use, and have made any appropriate renaming of the columns, place the tables and queries into your SSS [horses] database and run each of the Append queries to update your existing tables. 4) ADD NEW TRACKS ----------------- For SSS, you will need to have added the two new tracks into the [statecodes] table. These are: 94 - Thi - Thailand, and 95 - Brz - Brazil. I have left my old track codes as they were. These are not part of the SSS race data, but are derived from the track numbers themselves. If I update them I may possibly then need to update numerous stats queries, so I probably won't bother. Certainly not in the short term. You can update yours if you want to. Don't delete the tracks that have 'left' the game though. 5) POLY SURFACE --------------- This is denoted by 'P'. Although the going for all the Poly races so far have been given as 'All-Weather' in the Sim Results, the database entry in the data Mike has provided is given as 'fst'. 6) RACE NUMBERING AND SIM RESULTS DISPLAY ----------------------------------------- a) Race Numbering -------------- For stats purposes. and generally relating to the new Sim Results display, I have numbered the races at each track in serial order, in the order they are 'run' timewise, when the races are given 10 minute intervals. You may have noticed these are displayed now in 'reverse order', with the latest race at the top of the list. So, if there are 16 races at a track on a particular day then, all running at 10-minute intervals, they relate to the races in my tables such that the top-displayed at the Sim Results page is race 16, and the bottom- displayed is race 01. In cases where two or more races are shown in the Sim Results as running at the same time at a track (this occurs if a race 'splits' due to a large number of entries, but there have also been meets where all races are shown as running at the same time: 6:00pm, say) then the numbering in my tables is still 01 for the race at the bottom of the Sim page, and incrementing coming up the page. b) Sim Results Display - pre-changeover races ------------------------------------------ What I have stated in the previous section does NOT apply to pre-changeover races run up until noon on Sat Sep 1st, 2012 (week 5156). All these races display in the Sim Results in 'top to bottom' order, race 01 to race 16 for Saturday races. There were a number of races run at 6:00pm on Saturday (after normal Saturday racing for that last 'OldSim' day) [see Appendix 2 for detail of races run between end of 'OldSim' and changeover time] and this will hopefully demonstrate exactly how this affects things. Open up the Sim Race Results for 2012-09-01 to 2012-09-01, ticking Western Americas at the top, then clicking on the link for California on the left hand side. In addition to the normal races 1-16 run at noon that last 'OldSim' Saturday 5156, two races were run at 6:00pm. The races appear on the Results page in the order: 18, 17, 01, 02, 03...... 16. 7) HORSE NAMES AND TAGS ----------------------- a) Normal Horses ------------- As you will know, horses in the new Sim now don't show their tags as part of their names. In order to maintain consistency in the SSS tables, all horses that were in the Horse Pool (breeding file) at the end of week 5156 have had their tags added back in my tables, in addition to retaining their old Sim ID numbers. Horses bred in the new Sim are shown without tags. b) Naming Reversions ----------------- During the conversion process, a number of horses which had previously been renamed by Mike for various reasons have suffered reversion to their previous names. A couple or so other names have also changed for no apparent reason. I believe I have 'caught' all these and they are in the tables, or will appear in the tables when they race, with their CURRENT (reverted) name along with their old horse ID. If you look at horse 52079 you will see what I mean. 8) START SPEED -------------- As I have written elsewhere, Mike is no longer going to produce this figure. It was always an 'unofficial' figure drawn from the raceout data that powered the old downloadable offline Viewer, and it's not part of his new program output I am hopeful that I can eventually come up with a suitable replacement based on the split times for the first 2 furlongs, which are now part of the data Mike supplies. In the meantime, the SSS won't display if the ST field is left blank, so I have replaced it with '-999' for the time being. 9) 'HOT' RACES - week 5297 on ----------------------------- 'HOT' races were introduced in week ending Sun Jan 20th 2013 (5297). Most contests will not want these races included in their scoring, so these races are now denoted in my SSS Update Files by means of a claim-price value of "1" in the [tblraces] 10) DATE CALCULATOR ------------------- I will eventually make available a standalone date calculator (like the one in the current SSS, but with the day of the week included) which will convert between dates and 'week numbers' as soon as I can, after dealing with the raceout maker, and having got up to date with the result tables. ========================================================================== APPENDIX 1 - New Horse IDs -------------------------- New Sim Horse IDs are now 10 or 11 digits long. The first 2 (of 10) or 3 (of 11) digits indicate the year the horse was or will be 3yo. The remaining 8 digits are (generally) serially increased for each new 'birth': 9000000001+ = 1990 9100000001+ = 1991 etc 10000000001+ = 2000 etc 11200000001+ = 2012 11300000001+ = 2013 Current 3yos (in 2012) have IDs starting 112 Current 2yos (in 2012) have IDs starting 113 The oldest horses in the active Sim Horse Pool (12yos) have IDs starting 103 Horses in my [tblhorsedata] [hid_short] field still carry the old Sim ID if they were in the 5156 breeding file, otherwise their ID is offered in a modified version to enable use of the files in the existing SSS version 4.33 a) Up to w/e 8195 (Sun Dec 27th 2020) hid_short IDs have their leading '1' removed: eg: new Sim ID 11200000001 SSS version 1200000001 b) From w/e 8202 (Sun Jan 3rd 2021) hid_short IDs have their leading '1' removed, and also, if digits 2 and 3 are 22 or greater, their 4th digit, which is zero: eg: new Sim ID 12200000001 SSS version 220000001 This is because the data-type in the SSS is otherwise broken with the new 2yo IDs commencing with 122. (The number is otherwise too big). ========================================================================== APPENDIX 2 - Races run between noon 5156 and changeover ------------------------------------------------------- The following races were run, and are included in my tables: 5 races on Sat Sep 1st, 2012 at 6pm (still 5156) CA: 0117,0118 ID: 3017,3018 HK: 6017 5 races on Sun Sep 2nd at 6pm BC: 6901-6905 1 race on Mon Sep 3rd at 6pm NM: 1401 16 races on Tue Sep 4th :: 3 @ 10am, 8 @ 2pm, 5 @ 5pm All in supplied data (week 5159) ========================================================================== APPENDIX 3 - Ownername contractions ----------------------------------- In order to accommodate new longer character names within the existing SSS v4.33, I have modified those that have so far appeared: w/e 5164, w/e 5171 ------------------ The first 7 characters and last 2 characters of the name are retained. The removed characters are replaced with an underscore. eg: (11 example) littlefalls became littlef_ls and (12 example) christianp73 became christi_73 Unfortunately, longer names were processed by this method: eg: blackdiamond (12 characters) and blackdiamond0 (13 characters) were both imported as blackdiamond (truncated to 12 characters) and then contracted to blackdi_nd w/e 5178 - 5605 --------------- Three final characters are retained, eg: full [oname] [oname_12] [oname_10] -------------------------------------------------- littlefalls 11 -> littlefalls little_lls blackdiamond 12 -> blackdiamond blackd_ond blackdiamond0 13 -> blackdia_nd0 blackd_nd0 surfcatstables 14 -> surfcats_les surfca_les surfcatstables1 15 -> surfcats_es1 surfca_es1 w/e 5612 onward --------------- Three final characters are retained, but names up to 18 characters are now accomomodated {see Notes 'w/e 5612 (Dec 1st 2013)' at the Head of this document} eg: full [oname] [oname_15] [oname_12] [oname_10] -------------------------------------------------------------------- littlefalls 11 -> littlefalls littlefalls little_lls blackdiamond 12 -> blackdiamond blackdiamond blackd_ond blackdiamond0 13 -> blackdiamond0 blackdia_nd0 blackd_nd0 surfcatstables 14 -> surfcatstables surfcats_les surfca_les surfcatstables1 15 -> surfcatstables1 surfcats_es1 surfca_es1 eddiejrcolongon0 16 -> eddiejrcolo_on0 eddiejrc_on0 eddiej_on0 eddiejrcolongon25 17 -> eddiejrcolo_n25 eddiejrc_n25 eddiej_n25 eddiejrcolongon999 18 -> eddiejrcolo_999 eddiejrc_999 eddiej_999 w/e 5703 -------- For the first time, there was a name-clash (duplicate) on the 12- and 10- character owner name contractions this week. I have manually amended these contractions as shown below, with the thinking that later names such as silversun10epic1 might arise. full [oname] [oname_15] [oname_12] [oname_10] -------------------------------------------------------------------- existing -------- silversunepic1 14-> silversunepic1 silversu_ic1 silver_ic1 new name wk5703 --------------- silversun9epic1 15-> silversun9epic1 silversu_ic1 silver_ic1 manually amended to >>>>>>>> sil_un9epic1 sil_9epic1 Ongoing instances such as these will be documented in a weekly file in the SSS Update Pack. ========================================================================== END OF FILE - Denovo: Jan 8th 2021 (re: week 8202) ==========================================================================