
Laura,
They are different animals, with definite roles and mutual relationships. You do not have to choose one or the other. Of course there are some areas of possible overlapping. Simple database management tasks could also be accomplished by SPSS, such as merging files, as there are some simple statistical tasks that can be done by Access, like getting a crosstabulations or an average, but on the whole each software should be used for the kind of task it was intended for. You can prepare a crosstabulation with either package (as you can with Excel too), but do not try Cox Regression on Access. Preparing a flat table or file with a combination of variables taken from several levels of a hierarchical/relational database is better done with Access, though it is awkwardly possible also in SPSS. Looking for individual cases fulfilling certain conditions can be done with SPSS, but it is easier if done with Access. Hector
Hi Larua: Without getting too technical Ms Access is a good tool to store vast amounts of data in table format and comes with built in wizards/tools to create forms to get the data into those tables. If its manually data entry. Their are other methods to automate to the entry into the database. A quite and dirty explaination of 1 to Many relationships.....
Ms Access has a way to enforce integrity of the data by creating relationships amongst the tables. For example, 1 Director may have Many Staff members. In this case we have a table called Directors with only directors stored in it. and a table called Staff with only staff stored in it. Each director would only be stored once in the director table and is unique. This director can be stored in the Staff table many times denoting the staff associated with that director. Hence a 1 to Many Relationship. For Using both SPSS and Access database. Note: I have renamed some field names here to hide the some of the structure of my database. But the concept here remains the same.. Maybe you could leverage the skill sets and work with both tools hand in hand. This example shows how your Skilled Ms Access people would create a query for you to access an Access database to grab some data and push into the SPSS data editor. Then maybe you could use your SPSS skills to do the rest of the magic.
GET DATA /TYPE=ODBC /CONNECT= 'DSN=MS Access Database;DBQ=C:\SomeDataBase.mdb;DriverId=281;FIL=MS Access;MaxBufferSize=2048;PageTimeout=5;' /SQL = " SELECT IIF(IsNull(P.DECEASED), 0, IIF(P.DECEASED= 'N', 0, IIF(P.DECEASED= 'Y', 1))) AS 'Staff Died', " " (( IIF(T.StaffFailed= 'Y', T.DATE_Failed , DATE() ) - T.StaffFailed) / 365 ) AS 'Staff Survival' , " " (( IIF(P.DirectorFailed= 'Y', P.DATE_Failed, DATE() ) - T.DirectorFailed) / 365 ) AS 'Director Survival', " " IIF(IsNull(T.StaffFailed0, IIF(T.StaffFailed= 'N', 0, IIF(T.StaffFailed= 'Y', 1))) AS 'Staff Failed', " " YEAR(T.StaffHired ) AS 'GroupYear', " " FROM STAFF P, Directors T, Class D " " WHERE T.ID = P.ID " " AND T.DirectorID= P.DirectorID " " AND D.ClassID= T.ClassID" " AND P.StaffType IN('2') " " AND T.DirectorsFromHere IN('Y') " " AND D.ClassPeople IN('N') " " AND T.StaffHired BETWEEN #2000-01-01# AND #2005-12-31# " " ORDER BY T.StaffHiredDate ASC " /ASSUMEDSTRWIDTH=255 . CACHE. EXECUTE. I hope this helps answers your question and helps with your decision.
Cheers, Terry
I would caution people that Access (and Excel) can store vast amounts of data in the row direction, but it can only hold 255 columns in any table or query. This is a limit we've recently exceeded in some of the genetic work we're doing, and I'm relying more and more on SPSS's data/merge commands to assemble the output of several different queries into a single dataset. Databases like mySQL, MS SQL, and, I assume, Oracle are not as limited. Another caution is that Access is more liberal about field names than the SQL standard. It's quite possible to have fully functional tables and queries that cannot be called from outside Access. We have many dozens of queries that have evolved over the years that we would like to call directly from SPSS using an ODBC connection (there's a database wizard for this), but because the variable names use hyphens or other "special" characters, they cannot be called without modification. Most of the time we export data to files, then import those files into SPSS, when a database call directly from SPSS to Access would be much more efficient. This can be avoided with good planning and design. We use Access mostly for its tables and queries; for database management. For us, data entry takes place either by importing an Excel spreadsheet into an Access table (how we work with collaborators) or through a web-based form interface that runs with ColdFusion and Microsoft's webserver, IIS (how our clinicians enter data). I should also mention that it is possible to manipulate data programmatically by coding in Visual Basic for Applications, and we've created a few functions that perform simple statistical tasks, though for the heavy lifting we rely on SPSS (and StatView).
Eric
This is true. Another note on this. Access can only store upto 2GB of data. Oracle or SQL Server would be a wise and Truely RDMS. For SQL Server we can have up to 1024 columns for each row. Not sure on Oracle, tho they may be the same. As with anything in the deveopment world, their are more than one way to complete the same task. One would compare price , existing skill sets -->with requirements/desired functionality here. Thanks Eric.
Terry
Dr.
Here is the essence of the problem. Access is a relational data base. It does not have "columns" (that is until you get to designing report and talk about the placement of fields on a page). It is not a spreadsheet or a word processor. It requires a different way of think of the data. While a table can contain only 255 fields, a data base can contain many tables that can be and should be linked by a common field. Therefore you can reference many times 255 "columns". Also Access is sold and designed by Uncle Bill to be for "smaller" data sets. Microsoft SQL is designed by Uncle Bill for "larger" data sets. I have millions of records in my Access data bases. I know a very good accountant who does all his letters in Lotus. I also know a very good secretary who keeps large tables of number that she does mathematical calculations, on in WordPerfect. Both are convinced to the bone that their way is the "right way." It is what they know and "when all you have is a hammer you treat everything like a nail." If you want to do statistical analysis by using statistical analysis package, and if you want to store and sort data by using a data base package, just make sure they "talk" to each other when doing what they do best.
扫码加好友,拉您进群



收藏
