Runtime Error '3022' When Importing .dat Files Into Mvp Edit

[jonthefon]

So I was doing a roster update, using the simplistic in-game saving mode (which makes the .sav files) for the player ratings part of it, as it lets me quickly check on a player's "overall" rating as measured by their 'bar'.

Once I was finished with that, I used tywiggins' exporting tool to create the various .dat files from the .sav which was naturally loaded onto memory.

However, when I opened MVPEdit and attempted to import the .dat files to create a .mbe file, it stopped at the pitcher.dat file and gave me a "Run-time error 3022", citing how "the changes you requested to the table were not successful because they would create duplicate values in the index, primary key or relationship".

Anybody experienced this problem before, and managed to fix it?

or was it because I spent too much time loading, modifying and saving onto a .sav file? Because previously, I had managed to successfully turn data from a .sav to .dat files, then a .mbe file.

[DylanBradbury]

So I was doing a roster update, using the simplistic in-game saving mode (which makes the .sav files) for the player ratings part of it, as it lets me quickly check on a player's "overall" rating as measured by their 'bar'.

Once I was finished with that, I used tywiggins' exporting tool to create the various .dat files from the .sav which was naturally loaded onto memory.

However, when I opened MVPEdit and attempted to import the .dat files to create a .mbe file, it stopped at the pitcher.dat file and gave me a "Run-time error 3022", citing how "the changes you requested to the table were not successful because they would create duplicate values in the index, primary key or relationship".

Anybody experienced this problem before, and managed to fix it?

or was it because I spent too much time loading, modifying and saving onto a .sav file? Because previously, I had managed to successfully turn data from a .sav to .dat files, then a .mbe file.

I've had this problem too. Unfortunately, I had to completely recreate my rosters. The file was just too corrupt. Sorry I couldn't be more help, jonthefon.

[jonthefon]

Thanks for replying at least :p

[DylanBradbury]

Thanks for replying at least

No problem! It's nice to help out polite people like yourself.

Hopefully you created backups of you roster. (Fingers crossed.)

[Gordo]

My main gripe was not importing teams to another mbe, saying it wasn't a valid met file, when everything was in place. I started fooling around with running MVPedit in Windows98 compatibility mode. Early indication is that it helped, but that could just be coincidence.