Pseudo-Lahman database problems: Any suggestions?

BMW · 07-31-2006, 04: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?

BMW · 08-01-2006, 12:04 AM

I need more feedback than "Error: Historical Season cannot be imported!"

blackrussian · 08-01-2006, 04:26 AM

while i cant shed too much light for you, ive had the exact same problem when trying to create my own custom lahman db...and i cant for the life of me figure out why it wont import. i spent literally two days combing through every possible detail (referencing the original and mods like arod23/garlon's) and still no success.

the strange part is that i can import individual players but not full seasons. any of the db makers have ideas? i can post my files for someone to look at.

BMW · 08-01-2006, 10:56 AM

http://www.cbabaseball.com/cbadb.zip is the location of my files.

Nukester · 08-01-2006, 11:44 AM

Ill take a peek too

andymac · 08-01-2006, 11:51 AM

I have had this problem when there is an extra line left at the bottom of your csv file. Make sure you don't have a blank line in any of your files.

BMW · 08-04-2006, 03:03 PM

I finally discovered the biggest stumbling block when importing a user-created database.

My guess is that OOTP is hard-coded to recognize two leagues, "AL" and "NL". (Perhaps the FL (Federal League 1914-1915, but I didn't test this.) This is how the data imports and you magically see the American League (with DH) and the National League (without DH). If you look at the csv files, there is no place where the full name of the league is stored, and certainly no info about league rules.

So as soon as I converted by league acronyms in the Teams.csv file from "UL" and "FL" to "AL" and "NL", the import started.

07-31-2006, 04: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?

08-01-2006, 04:26 AM	#3
blackrussian All Star Reserve Join Date: Apr 2002 Posts: 954	while i cant shed too much light for you, ive had the exact same problem when trying to create my own custom lahman db...and i cant for the life of me figure out why it wont import. i spent literally two days combing through every possible detail (referencing the original and mods like arod23/garlon's) and still no success. the strange part is that i can import individual players but not full seasons. any of the db makers have ideas? i can post my files for someone to look at. __________________ v'

08-01-2006, 11:51 AM	#6
andymac Hall Of Famer Join Date: Feb 2002 Location: Effingham, IL Posts: 5,725	I have had this problem when there is an extra line left at the bottom of your csv file. Make sure you don't have a blank line in any of your files. __________________ June Madness: Links FTB: andymac

08-01-2006, 12:04 AM	#2
BMW Hall Of Famer Join Date: May 2003 Location: New Jersey Posts: 2,030	I need more feedback than "Error: Historical Season cannot be imported!"

08-01-2006, 10:56 AM	#4
BMW Hall Of Famer Join Date: May 2003 Location: New Jersey Posts: 2,030	http://www.cbabaseball.com/cbadb.zip is the location of my files.

08-01-2006, 11:44 AM	#5
Nukester All Star Starter Join Date: Dec 2001 Location: Newburgh, NY Posts: 1,923	Ill take a peek too

08-04-2006, 03:03 PM	#7
BMW Hall Of Famer Join Date: May 2003 Location: New Jersey Posts: 2,030	I finally discovered the biggest stumbling block when importing a user-created database. My guess is that OOTP is hard-coded to recognize two leagues, "AL" and "NL". (Perhaps the FL (Federal League 1914-1915, but I didn't test this.) This is how the data imports and you magically see the American League (with DH) and the National League (without DH). If you look at the csv files, there is no place where the full name of the league is stored, and certainly no info about league rules. So as soon as I converted by league acronyms in the Teams.csv file from "UL" and "FL" to "AL" and "NL", the import started.