--- "Rod Nelson" <rnelson@...> wrote:
> Not to take anything from Sean L., but to give credit where it
> is due about the origins of the database, I point you to this file:
> http://sabr.org/cmsfiles/PalmerDatabaseHistory.pdf
>
> I think it is important for anyone that uses this historical
> baseball data to understand its history.  Further suggested
> reading is "The Numbers Game:
> Baseball's Lifelong Fascination with Statistics" by Alan Schwarz.
> http://www.alanschwarz.com


The implication here, which has been made repeatedly, is that the
baseball database that I published was simply copied/stolen from
Palmer, and that just isn't true.  It's an old canard trotted out by my
detractors and by those who are fundamentally opposed to the idea of
making the data available in its raw form.

Rod's sugestion that I have not given credit where it's due is, I
think, completely unfair. Obviously the underlying statistical data
benefits from the work of all of the researchers mentioned in that
article at SABR.org as well as many others who it does not mention.  I
have credited those sources in the documentation at baseball1.com
(http://baseball1.com/statistics/readme53.txt).   The current readme
file on my website acknowledges the work of not only Palmer but also
Turkin, Thompson, Neft, Ruane, Spatz, Carle, Vincent, Dave Smith, and
maybe 40 other names, as well as SABR and several of its committtes,
the Baseball Hall of Fame, and Retrosheet. If there is anybody who I
have failed to acknowledge, please let me know, but please don't accuse
me of taking credit for other people's work.


In his 1984 Baseball Abstracts, Bill James wrote a whole chapter
lamenting the fact that researchers didn't have access to raw baseball
statistics. Ten years later, I took the initiative to resolve that
problem.  I didn't conjur the batting statistics out of the air... I
took them from existing sources.  I didn't disceren the yearly voting
totals for the various awards from my imagination... I culled them from
guides and encyclopedias and microfilm.  What I did was to collect all
of this existing information, integrate it together in one central
place, organize it in a way that would be useful, and make it
avavailble in digital form for free.

Most of the people involved in the Baseball Databank understand the
value of that work.  I know that the existence of the Database has
inspired new researchers and help foster important new work, because I
hear from researchers and I see the books and articles which cite the
Database as a resource.  Forman's baseball-reference website -- which I
think might be the most significant advancement for baseball research
in my lifetime -- uses that Database as its foundation.  The existence
of the Database has also been a boon for gamers, who now can easily
simulate any major league season using import functions built in to
most of the best selling baseball sims.

I think these are all positive things. Some people, I suppose do not.
Some people are opposed to my making the data available because it
makes it harder for them to sell it.  I understand that.  Some people --
  like Allan Schwarz -- oppose the laws that make statistical data not
protected by copyright.  They believe in the sweat of the brow
doctrine, and feel that re-using data somebody else has compiled is
morally wrong. Others feel that they need to defend Palmer becuase I've
wronged him. Look, Pete and I are on good terms.  I count him as a
personal friend.  We've worked on six or eight books together,
including the new ESPN Football Encyclopedia which came out this
summer.

If we need to rehash this old conversation again then let's do it.  But
please, at some point, can't we just move on?

Regards,
Sean Lahman

--- "Rod Nelson" <rnelson@...> wrote:
> Not to take anything from Sean L., but to give credit where it
> is due about the origins of the database, I point you to this file:
> http://sabr.org/cmsfiles/PalmerDatabaseHistory.pdf
>
> I think it is important for anyone that uses this historical
> baseball data to understand its history. Further suggested
> reading is "The Numbers Game:
> Baseball's Lifelong Fascination with Statistics" by Alan Schwarz.
> http://www.alanschwarz.com

The implication here, which has been made repeatedly, is that the
baseball database that I published was simply copied/stolen from
Palmer, and that just isn't true. It's an old canard trotted out by my
detractors and by those who are fundamentally opposed to the idea of
making the data available in its raw form.

Rod's sugestion that I have not given credit where it's due is, I
think, completely unfair. Obviously the underlying statistical data
benefits from the work of all of the researchers mentioned in that
article at SABR.org as well as many others who it does not mention. I
have credited those sources in the documentation at baseball1.com
(http://baseball1.com/statistics/readme53.txt). The current readme
file on my website acknowledges the work of not only Palmer but also
Turkin, Thompson, Neft, Ruane, Spatz, Carle, Vincent, Dave Smith, and
maybe 40 other names, as well as SABR and several of its committtes,
the Baseball Hall of Fame, and Retrosheet. If there is anybody who I
have failed to acknowledge, please let me know, but please don't accuse
me of taking credit for other people's work.

In his 1984 Baseball Abstracts, Bill James wrote a whole chapter
lamenting the fact that researchers didn't have access to raw baseball
statistics. Ten years later, I took the initiative to resolve that
problem. I didn't conjur the batting statistics out of the air... I
took them from existing sources. I didn't disceren the yearly voting
totals for the various awards from my imagination... I culled them from
guides and encyclopedias and microfilm. What I did was to collect all
of this existing information, integrate it together in one central
place, organize it in a way that would be useful, and make it
avavailble in digital form for free.

Most of the people involved in the Baseball Databank understand the
value of that work. I know that the existence of the Database has
inspired new researchers and help foster important new work, because I
hear from researchers and I see the books and articles which cite the
Database as a resource. Forman's baseball-reference website -- which I
think might be the most significant advancement for baseball research
in my lifetime -- uses that Database as its foundation. The existence
of the Database has also been a boon for gamers, who now can easily
simulate any major league season using import functions built in to
most of the best selling baseball sims.

I think these are all positive things. Some people, I suppose do not.
Some people are opposed to my making the data available because it
makes it harder for them to sell it. I understand that. Some people --
like Allan Schwarz -- oppose the laws that make statistical data not
protected by copyright. They believe in the sweat of the brow
doctrine, and feel that re-using data somebody else has compiled is
morally wrong. Others feel that they need to defend Palmer becuase I've
wronged him. Look, Pete and I are on good terms. I count him as a
personal friend. We've worked on six or eight books together,
including the new ESPN Football Encyclopedia which came out this
summer.

If we need to rehash this old conversation again then let's do it. But
please, at some point, can't we just move on?

Regards,
Sean Lahman

I have found the following three tables contain rows which do not have a master
record
associated with them.  In two cases, it appears to be a typographical error.  I
do not know
what the case is for the third table.

chad


SchoolsPlayer:
playerID
smithhi99


AwardShareManager
yearID  managerID
1988   treboto99m  (should this be trebeto99m ?)


FieldingOF
yearID   playerID
1882     geisem01  (should this be geissem01 ?)

Sean - I was sincere in the intro to my post in saying I meant not to take
anything from the valuable work that you've done.  And for the record, I
absolutely agree that Sean Forman (and David Smith's) contributions to the
of baseball research community are monumental.  I certainly did not mean to
rehash any dialogue that anyone might view as antagonistic, I only wanted to
point to Palmer's essay which I had hoped to be enlightening to many folks
in this forum, because we all stand on the shoulders of the giants who came
before us.  I'm well aware that you've worked on Pete's team on numerous
occasions and that there is no ill will and never has been.  My reference to
Alan's book was to recommend what I feel is the best documentation of the
history of the metrics themselves, and tells the compelling people side of
story.  By my thinking, it's all need-to-know info although it is old news
to those on this list who have lived it.  Lord knows there those among us
that the pioneering work of our forebearers for granted, ascribing all
credit instead to Billy Beane.

Rod Nelson
Research Services Manager
www.sabr.org

The SchoolsPlayer entry looks like it should be Hilton Smith. I'm not near
my tables at this time, but he should have an entry of some sort in the
DB.

Regards,
Derek

On Fri, 1 Dec 2006, cekoski wrote:

> I have found the following three tables contain rows which do not have a
> master record associated with them.  In two cases, it appears to be a
> typographical error.  I do not know what the case is for the third
> table.
>
> chad
>
>
> SchoolsPlayer:
> playerID
> smithhi99
>
>
> AwardShareManager
> yearID  managerID
> 1988   treboto99m  (should this be trebeto99m ?)
>
>
> FieldingOF
> yearID   playerID
> 1882     geisem01  (should this be geissem01 ?)
>
>
>
> http://www.baseball-databank.org/
> Yahoo! Groups Links
>
>
>
>

When I try to use the MySQL scripts to create the tables and load data
into SQL Server, I get syntax errors. Are there any simple "search and
replace" commands I can run against the scripts that will allow me to
import the data into SQL Server?

Thx in advance,
todd

----- Original Message -----

From: turczytj

To: baseball-databank@yahoogroups.com

Sent: Saturday, December 02, 2006 11:00 AM

Subject: [baseball-databank] Using SQL Server

When I try to use the MySQL scripts to create the tables and load data
into SQL Server, I get syntax errors. Are there any simple "search and
replace" commands I can run against the scripts that will allow me to
import the data into SQL Server?

Thx in advance,
todd

Just taking a quick look, and this doesn't look
standard:

) TYPE=MyISAM;

I don't think this is either:
  KEY playerID (playerID),
   KEY managerID (managerID),
   KEY hofID (hofID),
   KEY lahman40ID (lahman40ID),
   KEY lahman45ID (lahman45ID)

"enum" doesn't look standard.

smallint unsigned might give you problems

I would make everything either a varchar2 (in Oracle)
number, or double (for salary).

Tom


---------------------------------------------
http://www.InsideTheBook.com
The Book--Playing The Percentages In Baseball











-----------------------------------



________________________________________________________________________________\
____
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

There are lots of differences between MySQL and MS SQL, especially in
the accceptance of later SQL standards (SQL92, SQL99 and SQL03).
MyISAM is the standard type for MySQL (helps id the command as a MySQL
one)
e-mail me a copy of the script and I'll see what I can figure out.

--- In baseball-databank@yahoogroups.com, "turczytj" <turczytj@...> wrote:
>
> When I try to use the MySQL scripts to create the tables and load data
> into SQL Server, I get syntax errors. Are there any simple "search and
> replace" commands I can run against the scripts that will allow me to
> import the data into SQL Server?
>
> Thx in advance,
> todd
>

Correct, the "Type=MyISAM" caused problems along with the "drop
table" syntax. The "Key" commands also were problems. It seems that
there are probably SQL Server equivalents, but I don't know the
correct syntax to do a global "search and replace" operation. I was
hoping somebody here has already figured it out...


--- In baseball-databank@yahoogroups.com, Tangotiger <tangotiger@...>
wrote:
>
> Just taking a quick look, and this doesn't look
> standard:
>
> ) TYPE=MyISAM;
>
> I don't think this is either:
>  KEY playerID (playerID),
>   KEY managerID (managerID),
>   KEY hofID (hofID),
>   KEY lahman40ID (lahman40ID),
>   KEY lahman45ID (lahman45ID)
>
> "enum" doesn't look standard.
>
> smallint unsigned might give you problems
>
> I would make everything either a varchar2 (in Oracle)
> number, or double (for salary).
>
> Tom
>
>
> ---------------------------------------------
> http://www.InsideTheBook.com
> The Book--Playing The Percentages In Baseball
>
>
>
>
>
>
>
>
>
>
>
> -----------------------------------
>
>
>
>
______________________________________________________________________
______________
> Do you Yahoo!?
> Everyone is raving about the all-new Yahoo! Mail beta.
> http://new.mail.yahoo.com
>

If MyISAM is giving you problems then that means your using a newer
version of MySQL that is using the InnoDB data storage engine (later
version 4 and MySQL 5).  If you are you can open the .sql file in a
standard text editor and remove all of the TYPE=MyISAM.  Do not remove
the ";" at the end.  You should then be able to execute the file.

Command-line access to MySQL can be a pain.  I use a GUI front end
like MySQL Front or MySQL Navigator to help.


--- In baseball-databank@yahoogroups.com, "turczytj" <turczytj@...> wrote:
>
> Correct, the "Type=MyISAM" caused problems along with the "drop
> table" syntax. The "Key" commands also were problems. It seems that
> there are probably SQL Server equivalents, but I don't know the
> correct syntax to do a global "search and replace" operation. I was
> hoping somebody here has already figured it out...
>
>
> --- In baseball-databank@yahoogroups.com, Tangotiger <tangotiger@>
> wrote:
> >
> > Just taking a quick look, and this doesn't look
> > standard:
> >
> > ) TYPE=MyISAM;
> >
> > I don't think this is either:
> >  KEY playerID (playerID),
> >   KEY managerID (managerID),
> >   KEY hofID (hofID),
> >   KEY lahman40ID (lahman40ID),
> >   KEY lahman45ID (lahman45ID)
> >
> > "enum" doesn't look standard.
> >
> > smallint unsigned might give you problems
> >
> > I would make everything either a varchar2 (in Oracle)
> > number, or double (for salary).
> >
> > Tom
> >
> >
> > ---------------------------------------------
> > http://www.InsideTheBook.com
> > The Book--Playing The Percentages In Baseball
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > -----------------------------------
> >
> >
> >
> >
> ______________________________________________________________________
> ______________
> > Do you Yahoo!?
> > Everyone is raving about the all-new Yahoo! Mail beta.
> > http://new.mail.yahoo.com
> >
>

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the baseball-databank
group.

   File        : /BDB.mssql
   Uploaded by : westbaystars <westbaystars@...>
   Description : MS SQL Creation File for BDB.

You can access this file at the URL:
http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

westbaystars <westbaystars@...>

There's a great feature in MySQL for handling the differences between
databases.  I executed the following from the command line:

     $ mysqldump --compatible=mssql --no-data BDB > BDB.mssql

and have uploaded the BDB.mssql file to the files section on Yahoo!
Groups.

Open source solutions tend to provide better portability between
databases (and not just in one direction) with their tools than
proprietary ones, although by default they're going to be optimized
for their own needs.

The MyISAM type, for example, is to assure that the database storage
on a table by table basis will be the same way between various
versions of MySQL, even the same versions compiled with different
defaults.

Note:  You couldn't pay me use anything by Microsoft, so I have
        not tested the file.  Also, I'm still using last year's
        BDB, but don't think that the file structures have changed.

Hope this helps.

--
Michael Westbay
Writer/System Administrator
http://JapaneseBaseball.com

"P Mondout" <awesome80s@...> wrote:
>
> It can certainly be argued that this group exists to distribute the
> CSVs and that it is up to the end user to take it from there. I know
> this was discussed here about a year ago, but it would be great if we
> could collectively put together instructions for
> importing/manipulating the CSV files into common databases.

I agree with that sentiment.  This group shouldn't be occupied with
basic database support for end users.  However, issues of importing
data do have serious implications for general design. I think it's
important that we discuss those issues here.

The files section has some scripts and shells for importing the
database into MS Access.  Doing the same thing for other DBs is
probably a good idea, if we have members with that expertise.  Even
creating some text files to walk tech-savvy people through the process
would be helpful.

Keep in mind that this group is designed to assist power users, people
developing third-party apps, and people working to manage and maintain
the data.  For the vast majority of the end users, all of the things
we're discussing here are way over the head or more detail than they
care to see.

--Sean

I tried running the following query (it was typical of most of the
commands to create the database tables) and received the error
displayed at the bottom:

DROP TABLE IF EXISTS "Schools";
CREATE TABLE "Schools" (
   "schoolID" varchar(15) NOT NULL default '',
   "schoolName" varchar(255) NOT NULL default '',
   "schoolCity" varchar(55) default NULL,
   "schoolState" varchar(55) default NULL,
   "schoolNick" varchar(55) default NULL,
   PRIMARY KEY  ("schoolID"),
   KEY "schoolID" ("schoolID","schoolName")
);

Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'IF'.
Msg 156, Level 15, State 1, Line 9
Incorrect syntax near the keyword 'KEY'.



--- In baseball-databank@yahoogroups.com, baseball-
databank@yahoogroups.com wrote:
>
>
> Hello,
>
> This email message is a notification to let you know that
> a file has been uploaded to the Files area of the baseball-databank
> group.
>
>   File        : /BDB.mssql
>   Uploaded by : westbaystars <westbaystars@...>
>   Description : MS SQL Creation File for BDB.
>
> You can access this file at the URL:
> http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql
>
> To learn more about file sharing for your group, please visit:
> http://help.yahoo.com/help/us/groups/files
>
> Regards,
>
> westbaystars <westbaystars@...>
>

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the baseball-databank
group.

   File        : /BDB.mssql
   Uploaded by : westbaystars <westbaystars@...>
   Description : Updated MS SQL creation script for Baseball-Databank

You can access this file at the URL:
http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

westbaystars <westbaystars@...>

Turczytj-san wrote:

> I tried running the following query ... and received the error
> displayed at the bottom:
>
> DROP TABLE IF EXISTS "Schools";
> . . .
>
> Msg 156, Level 15, State 1, Line 1
> Incorrect syntax near the keyword 'IF'.

A little Googling shows that MS SQL doesn't support DROP TABLE IF
EXSIT table_name syntax.  If you want that functionality, it is
explained on this post:

     http://www.truevision3d.com/phpBB2/viewtopic.php?t=12277

I've replaced the script with one generated using the following
command line in MySQL:

$ mysqldump --compatible=mssql --no-data --skip-opt BDB > BDB.mssql

I then replaced the BDB.mssql file in the baseball-databank files
section, so please re-download:

     http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql

and try again.

While I don't support Microsoft, I am willing to do what I can to help
people get things working.  Please let us know if this new script
works or not.

--

Michael Westbay

I fear that I didn't address the problem with line 9:

01> DROP TABLE IF EXISTS "Schools";
02> CREATE TABLE "Schools" (
03>   "schoolID" varchar(15) NOT NULL default '',
04>   "schoolName" varchar(255) NOT NULL default '',
05>   "schoolCity" varchar(55) default NULL,
06>   "schoolState" varchar(55) default NULL,
07>   "schoolNick" varchar(55) default NULL,
08>   PRIMARY KEY  ("schoolID"),
09>   KEY "schoolID" ("schoolID","schoolName")
10> );
11>
12> Msg 156, Level 15, State 1, Line 1
13> Incorrect syntax near the keyword 'IF'.
14> Msg 156, Level 15, State 1, Line 9
15> Incorrect syntax near the keyword 'KEY'.

That is, the KEY definition line.  Could you please substitute the word
"INDEX" for "KEY" on line 9 and give that a try?  If that works, I'll
write a quick SED script to fix it.

--
Michael Westbay
Writer/System Administrator
http://JapaneseBaseball.com

----- Original Message -----

From: turczytj

To: baseball-databank@yahoogroups.com

Sent: Monday, December 04, 2006 7:22 PM

Subject: [baseball-databank] Re: New file uploaded to baseball-databank

I tried running the following query (it was typical of most of the
commands to create the database tables) and received the error
displayed at the bottom:

DROP TABLE IF EXISTS "Schools";
CREATE TABLE "Schools" (
"schoolID" varchar(15) NOT NULL default '',
"schoolName" varchar(255) NOT NULL default '',
"schoolCity" varchar(55) default NULL,
"schoolState" varchar(55) default NULL,
"schoolNick" varchar(55) default NULL,
PRIMARY KEY ("schoolID"),
KEY "schoolID" ("schoolID","schoolName")
);

Msg 156, Level 15, State 1, Line 1
Incorrect syntax near the keyword 'IF'.
Msg 156, Level 15, State 1, Line 9
Incorrect syntax near the keyword 'KEY'.

--- In baseball-databank@yahoogroups.com, baseball-
databank@yahoogroups.com wrote:
>
>
> Hello,
>
> This email message is a notification to let you know that
> a file has been uploaded to the Files area of the baseball-databank
> group.
>
> File : /BDB.mssql
> Uploaded by : westbaystars <westbaystars@...>
> Description : MS SQL Creation File for BDB.
>
> You can access this file at the URL:
> http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql
>
> To learn more about file sharing for your group, please visit:
> http://help.yahoo.com/help/us/groups/files
>
> Regards,
>
> westbaystars <westbaystars@...>
>

Dietz-san wrote:

> I'm not sure why you would define a
> primary key SchoolID and then redefine it again in the key clause.

The KEY (only) clause is synonymous with INDEX.  It's to optimize
searches on either the school_id or school_name.

The PRIMARY KEY is only school_id.

--
Michael Westbay
Writer/System Administrator
http://JapaneseBaseball.com

There is still a syntax error associated with the key:

Msg 156, Level 15, State 1, Line 8
Incorrect syntax near the keyword 'KEY'.


--- In baseball-databank@yahoogroups.com, Michael Westbay
<westbaystars@...> wrote:
>
> Dietz-san wrote:
>
> > I'm not sure why you would define a
> > primary key SchoolID and then redefine it again in the key clause.
>
> The KEY (only) clause is synonymous with INDEX.  It's to optimize
> searches on either the school_id or school_name.
>
> The PRIMARY KEY is only school_id.
>
> --
> Michael Westbay
> Writer/System Administrator
> http://JapaneseBaseball.com
>

Hello,

This email message is a notification to let you know that
a file has been uploaded to the Files area of the baseball-databank
group.

   File        : /BDB.mssql
   Uploaded by : westbaystars <westbaystars@...>
   Description : Revised MS SQL creation script (one line after $): $ mysqldump
--compatible=mssql,no_key_options --no-data BDB --skip-opt | sed -e "s/^  KEY / 
INDEX /" > BDB.mssql

You can access this file at the URL:
http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql

To learn more about file sharing for your group, please visit:
http://help.yahoo.com/help/us/groups/files

Regards,

westbaystars <westbaystars@...>

turczytj-san wrote:

> There is still a syntax error associated with the key:
>
> Msg 156, Level 15, State 1, Line 8
> Incorrect syntax near the keyword 'KEY'.

I was afraid of that.  Did you try to substitute "INDEX" for "KEY" (but
not "PRIMARY KEY")?

Anyway, I've revised the generation command to read:

$ mysqldump --compatible=mssql,no_key_options --no-data BDB --skip-opt |
sed -e "s/^  KEY /  INDEX /" > BDB.mssql

(All one line after the $ prompt.)

Please re-download the SQL creation script from:

http://groups.yahoo.com/group/baseball-databank/files/BDB.mssql

and try again.

While it may not be this group's job to help people get the database
loaded, I'd still like to do what I can (even if it perpetuates
someone's dependency on Microsoft).

Those of you who are forced to use MySQL on Microsoft platforms, you can
download SED (and other *NIX standard utilities) from:

      http://unxutils.sourceforge.net/

Setup the execution PATH variable to include the extracted binary
directory to use from the command line.

After giving similar tools to a colleague (much older than this
collection), he really got into writing shell scripts to do a lot of
text manipulation tasks.  After gaining confidence with these tools,
he's been slowly moving over to using Linux more and more.

--
Michael Westbay
Writer/System Administrator
http://JapaneseBaseball.com

Obviously retrosheet.org will eventually produce gamelogs and event
files for the 2006 season (this usually happens in April) but I'm on a
bit of a time constraint.  I have until January 24th to get as much done
as I can while I'm on winter break.  I am hoping some of you will know
if anyone has done a reconstructive build of the 2006 event files
already in the same format if at all possible as the rest of
retrosheet's work.

I also have another quesztion...for the longest time I relied on KJOK's
parks database.  He seems to have foresaken that work however as his
most recent parks database is not updated beyond 2004.  Does anyone have
any suggestions as to where to get the same level of park information
for 2005 and 2006?

......
I also have another quesztion...for the longest time I relied on KJOK's
parks database. He seems to have foresaken that work however as his
most recent parks database is not updated beyond 2004. Does anyone have
any suggestions as to where to get the same level of park information
for 2005 and 2006?.....

.

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

I'm relieved to hear that KJOK...I'll pick up the latest copy post
haste.  Muchas garcias KJOK...you da man. :)

My other question remains.

In order to accomplish what I set out to get done this month, I need the
b-db, complete and up to date gamelogs (through 2006)  and 2006 event
files to merge with my current files.

Thanks in advance, guys. :)

hackersdienow wrote:
(snip)
>
> In order to accomplish what I set out to get done this month, I need the
> b-db, complete and up to date gamelogs (through 2006) and 2006 event
> files to merge with my current files.
>

There's a problem here, unfortunately - the MLB.com event logs from
which these files have been created in the past are missing a *lot* of
half-innings this year, which means a lot of manual editing to
reconstruct the missing plays (often having to go to video archives to
get the exact sequence of events). I know that I won't have this process
done any time soon in the files that I typically create.
--
Mike Emeigh
piratefan1@...

D'oh!  Of course.  My programmer ally finally gets a free couple of
weeks and naturally a problem like this would happen. *headdesk*

Thanks for the reply, sir.  I appreciate the response even if it does
doom my winter break.