Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open SOTG database in Scid #28

Open
GoogleCodeExporter opened this issue Oct 9, 2015 · 4 comments
Open

Can't open SOTG database in Scid #28

GoogleCodeExporter opened this issue Oct 9, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

I have a database which works fine in SOTG, but can't be opened in Scid vs. PC, 
throwing a name error. I can't repair the database, either, I get a "corrupt 
data reading" error.

What is the expected output? What do you see instead?
I'd like it to work. Otherwise, I have to mail 80 games to myself.

What version of the product are you using? On what operating system?
SOTG Android 4.2.1, Scid vs. PC on both Mac and PC


Original issue reported on code.google.com by jeremy.d...@googlemail.com on 27 Feb 2013 at 8:38

Attachments:

@GoogleCodeExporter
Copy link
Author

Now I'm glad I didn't remove the "experimental" from save game yet.

I've attached a repaired version of the file. I did this by opening the scid 
database in Chess PGN Viewer and adding each game to favorites.pgn and 
re-importing the pgn in Scid on the PC.

I guess the PGN export feature is getting more important now :-)

I don't know what caused the issue yet.

Original comment by gerhard....@gmail.com on 3 Mar 2013 at 11:43

  • Changed state: Accepted

Attachments:

@GoogleCodeExporter
Copy link
Author

Original comment by gerhard....@gmail.com on 3 Mar 2013 at 11:44

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Thanks Gerhard!

Original comment by jeremy.d...@googlemail.com on 5 Mar 2013 at 1:51

@GoogleCodeExporter
Copy link
Author

I've added the PGN export feature, so you have at least a workaround if it 
happens the next time.

Of course that's not a fix for the issue.

Original comment by gerhard....@gmail.com on 14 Mar 2013 at 10:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant