OOTP Developments Forums - View Single Post - Pseudo-Lahman database problems: Any suggestions?

BMW · 07-31-2006, 03:36 PM

I'm having issues trying to create a pseudo-Lahman Db. I'm using the same tables as the ARod23 database:

Master.csv
Teams.csv
TeamsFranchises.csv
Batting.csv
Pitching.csv
Fielding.csv
Fieldingof.csv

Unfortunatly my pseudo-Lahman db doesn't import. Since the error message is non-descript in what the problem is, (It just says something like "Historical Season cannot be imported!") I can't debug it efficiently.

I took care to actually use the identical MSAccess structure that Lahman uses and then export it to CSV.

I've tinkered different formats of the PlayerIDs (even though they should have provided a proper Primary => Foreign key relation), the Stint field that is present in most of the tables, the length of the TeamID and FranID fields (since Lahman seemed to always use all 3 characters allocated for the field length), even though these seem to be trivial issues. I've removed all the February 29th birthdays, parsed commas out of the nameNick and college fields (even though the actual Lahman csv DB seems to have commas in the nameNick field).

None of these seem to have worked. The ARod23 and Lahman csv files do import properly, so it shouldn't be something like a funky install.

Any ideas?

07-31-2006, 03:36 PM	#1
BMW Hall Of Famer Join Date: May 2003 Location: New Jersey Posts: 2,030	Pseudo-Lahman database problems: Any suggestions? I'm having issues trying to create a pseudo-Lahman Db. I'm using the same tables as the ARod23 database: Master.csv Teams.csv TeamsFranchises.csv Batting.csv Pitching.csv Fielding.csv Fieldingof.csv Unfortunatly my pseudo-Lahman db doesn't import. Since the error message is non-descript in what the problem is, (It just says something like "Historical Season cannot be imported!") I can't debug it efficiently. I took care to actually use the identical MSAccess structure that Lahman uses and then export it to CSV. I've tinkered different formats of the PlayerIDs (even though they should have provided a proper Primary => Foreign key relation), the Stint field that is present in most of the tables, the length of the TeamID and FranID fields (since Lahman seemed to always use all 3 characters allocated for the field length), even though these seem to be trivial issues. I've removed all the February 29th birthdays, parsed commas out of the nameNick and college fields (even though the actual Lahman csv DB seems to have commas in the nameNick field). None of these seem to have worked. The ARod23 and Lahman csv files do import properly, so it shouldn't be something like a funky install. Any ideas?