demonstrating use of pyodbc

[ghost]

See commit dae609c2b0cad702e49512c7d1b81da6d3331e43 for some sample pyodbc code to connect to the beast.

I couldn't find the most recent version of the db so I just grabbed the first I could find and made a local copy.

Here is the output I get when running the program:

table: archdescdid, rowcount=5735
table: archdescphysloc, rowcount=7412
table: BoxList, rowcount=128482
table: corpname, rowcount=4
table: eadheadercreationOLD, rowcount=281
table: eadheaderpublisher, rowcount=570
table: eadheaderpublisherOLD, rowcount=434
table: eadheaderrevision, rowcount=761
table: ItemList, rowcount=32327
table: resourceguide, rowcount=2437
table: rgnames, rowcount=40
table: seriesdesclist, rowcount=1559
table: seriestest, rowcount=102
table: source, rowcount=4668
table: sourcecopy, rowcount=2488
table: subjects, rowcount=2564
table: subseriesdesclist, rowcount=352
table: cas_coll_umd, rowcount=7630
table: qryURL, rowcount=5735

[jennielevineknies]

For the record, the most recent/active databases are located in M://Coll Mgmt & Spec Coll/Special Collections/EAD/databases/

I have added a sample, blank database to the EAD Converter ead-db-convert project: https://github.com/umd-lib/ead-db-convert/tree/develop/db Awaiting word from Amanda if I can load a data-filled one as an example for SCPA.

There are different databases for scpa, and for some of the different departments in Hornbake. They have form customizations in them, but the structure is essentially the same (they all work with the converter). The Access databases are split, and the data file itself is in the folders called "***BackEnd"