Bridgemate Error with NS Rover Mitchell

[mandurahbridge]

When using a 13.5 or 14.5 NS Rover Mitchell the following error is now reported by the Bridgemate Program

"Failed to Load rounds from Data Base for Table 14 (or 15)
Try to update movement manually from Session - Update movement.
Verify in Session - Edit movement the rounds for this table"

As there is no play on Table 14 (or 15) this would not seem to be a problem but we have used this type of movement in the past without the error appearing.

Regards

Neville Walker

[ianmac]

Have you updated the bridgemate software?
Maybe there is a change there?

[mandurahbridge]

Hi Ian
We updated to the latest version (1.720) a few weeks ago so it is possible this is the reason for the problem - should we liaise with Willem regarding this?
It is interesting to note that the Seating Draw for this movement does not show "0" as the pair number for the Sit Out Pair whereas for a Relay Mitchell with 13.5 tables it does.
We used the NS Rover yesterday and it worked fine
Neville

[Bridgemate]

Was the sit out at the highest table number and does it occur also when it starts at a different table?

I have to see the bws-file to see what happens with the sitout.
You could send the file using the special "service-report"-page on the website:
http://www.bridgemate.com.au/support_service.html

Willem

[mandurahbridge]

Hi Willem
Tables 14 (or 15) are the only ones used as the sit out for this type of movement - the NS pair from T14 sit our for the first round and then in a 13.5table movement replace the NS pairs sequentually at tables 2,4,6,8,10,12,1,3,5,7,9 and 11.

I will post the bws file to the site.

Neville

[ianmac]

We have had comments from the Bridgemate tech person on this.

"In case of a rover pair, there is no need to add the 14th table to the bws file, as there is no play happening at that table. When there is an empty table in the bws file, BPC will signal this. However, there is no further impact on the performance, and it won't harm the session.

However, very soon version 1.7.60 will be released and this will handle this a bit nicer. I don't think there is any need at this moment to change something in ASE8."