i’d be happy to try anything that works better than what we have now
It sure looked like it indexed it - it can search it for you or me by name or ID and then pull up all of our ratings?
I guess my question is what additional functionality you are expecting out of that file?
If I understood what others said, the FN LN vs LN,FN issue may have interfered with lookups by name.
I’ve got the latest SwissSys on my computer and I think I have it using the gold master blitz file, but lookup by name or id isn’t looking, though it seems to find them if I do a refresh from database.
I must have something set up wrong.
1 Like
I will play with it some more tomorrow. I just cut my index finger and typing is really slow.
latest tab file works with swissys fine once I change the file name still fiddling with DBF.
and i did get the december dbf blitz file to load into swissys once i changed the file name.
i will put these files on the legacy site with the right file names in the morning.
Might you find time to put ALLRTG2512.zip in its accustomed place as well?
That’s the legacy site.
I wasn’t sure if Mike was referring to just what SwissSys needs or all the versions of the supplement. Here’s hoping he means all of them.
Does anybody need the smaller monthly files? (about 115K records, I think, due to the database and programming changes made in late October.)
Not I, said the Little Red Hen. I use the Golden database for SwissSys. Last month’s was GDQ2511.zip. And last month WinTD downloaded ALLRTG2511.zip. So whatever the equivalent of those two for this month is what I need.
1 Like
now on secure2:
-rw-r–r-- 1 uscfdata22 uscfdata22 25342355 Nov 28 08:14 ALLRTG2512.zip
-rw-r–r-- 1 uscfdata22 uscfdata22 21694933 Nov 28 08:14 GDB2512.zip
-rw-r–r-- 1 uscfdata22 uscfdata22 23073268 Nov 28 08:14 GDQ2512.zip
There are still 2 unresolved data issues, one has to do with invalid characters and there is another report that some expiration dates are wrong that I have yet to check, but for those who need these files NOW, here they are.
WinTD will download that using 2025-12, but then will crash if you try and open the database.
First question:
ALLRTG2511.zip contains a single directory, ALLRTG2511, with readme.txt and rtglist.txt contained inside.
ALLRTG2512.zip contains a single directory, ALLRTG2512, with readme.txt and allplayers.txt contained inside.
Why did you change the filename inside the zip at the legacy site?
This does not look to be the right filename, containing “Uscf-2025-12-AllMembers-Quick.dbf” rather than “TARATSUP.DBF”. If renamed to TARATSUP.DBF it seems to do fine.
To recap:
Swissys, if pointed at a “TARATSUP.DBF” file from either GDB2512.zip or GBDQ2512.zip, seems to do fine, indexing on standard Golden defaults.
WinTD downloads the ALLRTG2512.zip but crashes in trying to process it, possibly because of the differing “allplayers.txt” filename insde.
My own personal program parsed allplayers.txt fine for what I use it for (building a custom WinTD players list of the club players [I built it when the update from database used to fail for quick ratings]).
My experience was the same as yours, for both WinTD and SwissSys. WinTD seems to rename the readme file as rtglist.txt. I notice that in previous downloads, the readme file is listed first. Could WinTD be grabbing the first file and making it into the rtglist.txt file? Mike, can you try zipping them in the opposite order? I see WinTD builds the uscfdata.dbf as soon as it downloads, but doesn’t index it until you try to use the database.
darn I thought I got those right That’s why I wrote a shell script file to do that task on the old system.
I’m at 50% speed at best today with a bandaged right index finger.
Archive: ALLRTG2511.zip
Length Date Time Name
--------- ---------- ----- ----
28 10-17-2025 11:29 ALLRTG2511/readme.txt
100526489 10-17-2025 11:29 ALLRTG2511/rtglist.txt
--------- -------
100526517 2 files
Archive: ALLRTG2512.zip
Length Date Time Name
--------- ---------- ----- ----
28 11-28-2025 07:35 ALLRTG2512/readme.txt
101008511 11-28-2025 07:35 ALLRTG2512/rtglist.txt
--------- -------
101008539 2 files
Archive: GDB2511.zip
Length Date Time Name
--------- ---------- ----- ----
1002 10-17-2025 11:45 GDB2511/README.txt
68469882 10-17-2025 11:45 GDB2511/TARATSUP.DBF
--------- -------
68470884 2 files
Archive: GDB2512.zip
Length Date Time Name
--------- ---------- ----- ----
1002 11-28-2025 07:57 GDB2512/README.txt
71624138 11-27-2025 14:00 GDB2512/TARATSUP.DBF
--------- -------
71625140 2 files
Archive: GDQ2511.zip
Length Date Time Name
--------- ---------- ----- ----
1002 10-17-2025 11:37 GDQ2511/README.txt
68469882 10-17-2025 11:37 GDQ2511/TARATSUP.DBF
--------- -------
68470884 2 files
Archive: GDQ2512.zip
Length Date Time Name
--------- ---------- ----- ----
1002 11-28-2025 07:59 GDQ2512/README.txt
71624138 11-27-2025 14:01 GDQ2512/TARATSUP.DBF
--------- -------
71625140 2 files
Looks great; it will be a while before I can verify, though.
There are a lot of records where the expiration date doesn’t match up, around 69K of them. I didn’t see a pattern yet but Leago is aware of this, as it might affect both types of files and be a problem on MUIR database as well.