Hi
In rd5 of the World Junior Championship (Hong Kong v Egypt) , Board 15 in the Open Room was Passed Out (shown as PASS in the rs | data at start of file); then all the other board results to end of match are not shown in the scoreboard screen using NetBridgeVu. This is strange, considering these results have been given in the rs| data. Does anyone know how to correct this apparent anomaly
Denis
Page 1 of 1
Passout in Lin file
#2
Posted 2003-August-20, 16:11
Quote
Hi
In rd5 of the World Junior Championship (Hong Kong v Egypt) , Board 15 in the Open Room was Passed Out (shown as PASS in the rs | data at start of file); then all the other board results to end of match are not shown in the scoreboard screen using NetBridgeVu. This is strange, considering these results have been given in the rs| data. Does anyone know how to correct this apparent anomaly
Denis
In rd5 of the World Junior Championship (Hong Kong v Egypt) , Board 15 in the Open Room was Passed Out (shown as PASS in the rs | data at start of file); then all the other board results to end of match are not shown in the scoreboard screen using NetBridgeVu. This is strange, considering these results have been given in the rs| data. Does anyone know how to correct this apparent anomaly
Denis
I suspect it is a capital P versus small p type problem.
Can you please send me a copy of the .lin file. This is
the one match I do not have the .lin file for yet.
My e-mail: fred@bridgebase.com
If the problem is not P/p related I will let you know
what it is.
Fred Gitelman
Bridge Base Inc.
www.bridgebase.com
#3
Posted 2003-August-21, 00:26
Fred has provided a fix for now and will modify the software for next issue - well done Fred & Thx again
Denis
"I changed the PASS in the rs| to a P and now
everything seems fine.
I will modify the software so that this will not
be a problem in the future, but the fix will not
go into effect until our next release.
Regards, Fred "
Denis
"I changed the PASS in the rs| to a P and now
everything seems fine.
I will modify the software so that this will not
be a problem in the future, but the fix will not
go into effect until our next release.
Regards, Fred "
Page 1 of 1