Hit,
I have been using Romcenter ver 3.40 to update my list of roms for both Mame and the various AMIGA roms. From time to time, in trying to close a ROM Path, I get the following error message:
Violation of FOREIGH KEY constraint"FK_FILESVIEW_1" on table "FILESVIEW" Foreign key references are present for the record At procedure 'P_REMOVEPATH' violation of FOREIGN KEY constraint "" Error code: 146.
I couldn't copy/paste the message for some unknown reason and had to type it manually.
If I close the database & reload it. The path I tried to close is still there and I get the same error message if I try to close it.
The only fix I found is to delete the RDT file and restart from scratch.....
By the way, thanks for one of the best renaming tool existing today...
Rgards,
Alain T.
Bug in RomCenter 3.40
Moderator: Wanderer
Forum rules
No roms requests or illegal links
No roms requests or illegal links
Re: Bug in RomCenter 3.40
Do you get the error message when using a MAME datafile, Amiga or in both cases?fastfinger wrote:From time to time, in trying to close a ROM Path
- Wanderer -
RomCenter: Main site, Bug reporting & enhancement requests, Wiki
RCDBManager: Main site, Bug reporting & enhancement requests, Wiki
RomCenter: Main site, Bug reporting & enhancement requests, Wiki
RCDBManager: Main site, Bug reporting & enhancement requests, Wiki
Re: Bug in RomCenter 3.40
This still occurs in 3.54 for a MAME data set.
Starting over by deleting rdt is probably safer, but I seemed to be able to clean up
the issue with this procedure as well:
1) Close the database
2) Move the directory of the ROM path you're trying to close to another name.
3) Make an empty directory with the original ROM path name
4) Open the database
5) Refresh the ROM path that was causing problems
6) Close the ROM path
7) Close the database
8) Move the directory of the ROM path back to the original name
After this I was able to open the database and open and close
the ROM path that was causing the problem at least once without
this error.
Starting over by deleting rdt is probably safer, but I seemed to be able to clean up
the issue with this procedure as well:
1) Close the database
2) Move the directory of the ROM path you're trying to close to another name.
3) Make an empty directory with the original ROM path name
4) Open the database
5) Refresh the ROM path that was causing problems
6) Close the ROM path
7) Close the database
8) Move the directory of the ROM path back to the original name
After this I was able to open the database and open and close
the ROM path that was causing the problem at least once without
this error.
Re: Bug in RomCenter 3.40
Thanks for the report.
I will check that.
I will check that.
Eric - RomCenter developer
Report bugs here.
Report bugs here.
Re: Bug in RomCenter 3.40
I don't know where the problem come from.
Could you describe what you did with your roms paths ?
Can you reproduce the problem ?
Can you send me a zipped database file with the problem (through rapidshare or similar site)?
Could you describe what you did with your roms paths ?
Can you reproduce the problem ?
Can you send me a zipped database file with the problem (through rapidshare or similar site)?
Eric - RomCenter developer
Report bugs here.
Report bugs here.