Search results

An odbc would be awesome to have. But there would be way to much red tape to get through because of the SNAP data being on a state server and those that are higher up will not let me touch anything in the way of linking. Unless there was a way to make an actual url link to the data. That is for...

jdraw, The only thing this (the one I am working on) database does is hold information on crocodiles and allow the user to query the information to find a specific crocodile and allow a user to input information on new crocodiles or new sightings of a crocodile. All other information in the SNAP...

ridders, LOL yes the name is a misnomer, however it was originally designed for alligators exclusively. Once the agency noticed that crocodiles were also being called in as nuisances the agency just piggybacked the crocodile calls into the same call center. Also the acronym SNAP sounds better...

jdraw, This database is for crocodiles only. Alligators are monitored via a completely different set of databases, and regulations. Pat, The measurements do in fact change over time. Should the biology table actually go in the sightings table? or should the biology table just have a FK from...

Pat, I think I understand. Because of the "handling" "magnets" and alive fields there is more than just location information in that table so the table name should reflect that. Locations can in fact repeat though GPS data prevents the location overlap. As far as the SNAP# it is generated...

Currently you are correct in that each specific record in the ID table refers to only one crocodile. However, it is theoretically possible that one of the identifiers could change. A tag could break off and need to be replaced, injury in the wild could change the SCP or the PIT tag could cease...

everything is part of the encounter. That is basically what the database is. A database of crocodile encounters. Location was separate but many other tables, as was explained to me, were based on the actual location of the encounter hence the new relationships. As far as the date fields It will...

ID is a table full of Identifying characteristics. Those include the SCP (Scute clip pattern) ,the PIT tag (internal tag), and the cattle tag (external tag) info. I had it called Identification before but figured ID would be easier as long as I renamed any PKs , which I think I forgot to do with...

Pat, Thanks for the suggestions!. I have just finished moving the Alive flag to the location table. As far as SNAP# that should be easy to move and shouldnt be a problem to do. However, I have changed the relationship to where biology and other info are linked to the Location as opposed to...

Oh and as far as reports. The main official one generated is every fiscal year. The database will mainly be used for querying crocodiles based on limited information. Tag color, partial SCP (Scute Clip Pattern) seen, ect.. This information helps CRAs in the field and is used in management decisions

Ok a description of the business: I am the crocodile response coordinator for FWC (state wildlife agency) When the public sees what they deem as a nuisance crocodile they call the SNAP (Statewide Nuisance Alligator Program) hotline. After that a SNAP# is created and location information and...

Business Rules: A. Scope A.1 Crocodile information and tracking B. Things of interest B1. Crocodiles B2. Biological measurements B3. Location B4. Reports B5. Notes B6. SNAP reference number B7. Sex B8. Alive B9. Date/Time B10. Identification C. These things are related as C1. A Crocodile can...

Mark, Unfortunately I donot have access to the original excel sheet and it is difficult to use size as a means of estimating date as sightings lack measurement data as the animal is not "worked-up"

I did have a previous thread back in December where I was having difficulty getting the select query to display what I wanted. That issue has been corrected and data split into various tables (it was all under one table previously). Im doing my best to normalize it. I will post business rules...

Ohhh the mushing is actually done via the query. Each value is stored separate and displayed in the format that is user friendly once the query is run. The data in the table is stored in separate fields and as text data as the pattern is separated by "/" So field S "5/10/12" field DL "2/6" and...

I cant really make dummy locations unless I use locations that do not actually exist, as one way you can look up a crocodile is by its location. Example: you want to know how many crocodiles were at location x for as data has been taken. You can run the search query for that. I guess I could...

Hey Pat, 1. I will delete Lookup. i think i created it because I wasnt sure how all my PKs would interact and I thought I was going to have a many-to-many relationship. 2. I have crocodile and ID separate because a crocodile can theoretically have multiple ID characteristics. For example, a...

jdraw, Thank you so much for your help and patience. Ill work through the tutorials and get back to you with the info that you requested. If not by the end of the business day today then tomorrow

I think I am a bit fuzzy as far as what is meant by "business rules." A better description of the end goal of the database. I want to be able to lookup the history of any crocodile in the database by any of the identifying characteristics (this currently works as desired). For instance if I...

Database requirements for this project are: 1. Store data on crocodile location and biological information as well as attached reports 2. Search database given few variables to determine history of crocodile or area in question 3.Produce reports for management I can add descriptions if needed...