|
|||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Display Modes |
|
|
#1 (permalink) |
|
Minors (Triple A)
Join Date: May 2003
Location: New Jersey
Posts: 258
|
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? |
|
|
|
|
|
#3 (permalink) |
|
All Star Reserve
Join Date: Apr 2002
Posts: 834
|
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' |
|
|
|
|
|
#4 (permalink) |
|
Minors (Triple A)
Join Date: May 2003
Location: New Jersey
Posts: 258
|
http://www.cbabaseball.com/cbadb.zip is the location of my files.
|
|
|
|
|
|
#5 (permalink) |
|
All Star Starter
Join Date: Dec 2001
Location: Newburgh, NY
Posts: 1,908
|
Ill take a peek too
__________________
Well, I don't really think that the end can be assessed as of itself as being the end because what does the end feel like? It's like saying when you try to extrapolate the end of the universe, you say, if the universe is indeed infinite, then how - what does that mean? How far is all the way, and then if it stops, what's stopping it, and what's behind what's stopping it? So, what's the end, you know, is my question to you. |
|
|
|
|
|
#7 (permalink) |
|
Minors (Triple A)
Join Date: May 2003
Location: New Jersey
Posts: 258
|
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. |
|
|
|
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|