SQL Error: Constraint Failed

[DenverMoose]

Hey there... I've been using Pinup Popper front end for a long while now.  I have a fairly large collection.  

 

Starting recently, when in the PinUp Popper Setup program and adding new tables, updating older tables, etc.... All of a sudden I get a pop up message that says "SQL Error: Constraint Failed".  The only way to get rid of it is shutting down the app and re-launching, but it comes back pretty quickly.  Not having any issues when the front end is running, but it's becoming more frequent when adding or updating tables etc.  

 

I searched the threads, so apologies if this covered elsewhere, but thought I'd reach out and see if anyone has any advice here. 

 

Thanks! 

[outhere]

https://www.nailbuster.com/wikipinup/doku.php?id=pinup_upgrade_v15https://www.nailbuster.com/wikipinup/doku.php?id=pinup_upgrade_v15

[wz66h1]

Hello All.  Any explainable answer to the question above on the constraint failure error when saving a game after replacing it in games manager.  Basically, after entering games manager and selecting the game to replace it with a new version say, it acknowledges that the game has been saved and all files have been updated.  I usually change the default exe to the visual pinball 64 bit version for the newer tables and press save and get the "SQL Constraint failure" error and have to exit and reenter to complete the change to 64bit vpx.  It does not seem to matter if you change to the 64bit exe though.  If you complete the update then click on another game to update it the SQL constraint failure occurs anyway then you have to exit and reenter games manager to do another.  All works in the long run.  Just a hassle having to exit and reenter.  Any help is greatly appreciated.  Running version 1.5 popper.  Thanks  -Bill

[outhere]

2 hours ago, wz66h1 said:

Hello All.  Any explainable answer to the question above on the constraint failure error when saving a game after replacing it in games manager.  Basically, after entering games manager and selecting the game to replace it with a new version say, it acknowledges that the game has been saved and all files have been updated.  I usually change the default exe to the visual pinball 64 bit version for the newer tables and press save and get the "SQL Constraint failure" error and have to exit and reenter to complete the change to 64bit vpx.  It does not seem to matter if you change to the 64bit exe though.  If you complete the update then click on another game to update it the SQL constraint failure occurs anyway then you have to exit and reenter games manager to do another.  All works in the long run.  Just a hassle having to exit and reenter.  Any help is greatly appreciated.  Running version 1.5 popper.  Thanks  -Bill

Sound like an older exe? are you using 'manual' updating of popper? (non baller install). check wiki page/updates/manually link to grab latest files.