Don want to use Paradoxs queries, graphs, or its other tools to do data analysis?
exporting Paradox tables to spreadsheets in this FAQ.) The other thing–and nearly as important–is that your queries will make MUCH more sense if you (or someone else) looks at them 6 mos or so after you initially wrote them, because they use field names which actually make sense for their data set type (method). Also, queries on extracted tables are MUCH quicker… they don’t have to wade through the irrelevant data which doesn’t correspond to the data set type you’re analyzing. The reason FIELDATA exists is so that you don’t have to keep up with all the data set types (methods) that you’ve created in case you want to ask a question about anywhere you’ve ever seen/any data you’ve ever collected about a particular SPECIES. (Also, it would be very tedious to do data entry into [or write programs for data entry into] completely normalized tables, like those created by the EXTRACT routines.
exporting Paradox tables to spreadsheets in this FAQ.) The other thing–and nearly as important–is that your queries will make MUCH more sense if you (or someone else) looks at them 6 mos or so after you initially wrote them, because they use field names which actually make sense for their data set type (method). Also, queries on extracted tables are MUCH quicker… they don’t have to wade through the irrelevant data which doesn’t correspond to the data set type you’re analyzing. The reason FIELDATA exists is so that you don’t have to keep up with all the data set types (methods) that you’ve created in case you want to ask a question about anywhere you’ve ever seen/any data you’ve ever collected about a particular SPECIES.
