Originally Posted by
ssanfu
I downloaded the zip file VURAM2.1.1.zip from DEQ's webpage - file size is 2,077 kb - so can't upload in the forum. (limit is 2 mb)
The dB is locked down tight- I spent about 10 minutes playing with it, then tried importing the objects into a new dB. About a third to a half of the dB wouldn't/couldn't be imported.
From the tables I was able to look at, there are serious naming issues (IMHO). There are spaces, special characters, punctuation and the occasional reserved word in the object names. Example of one field: SFO (mg/kg-day)-1
What tables have PK fields are text types. Can't tell how the tables are related.
That is where I stopped......
Thanks for trying, Steve. Yes, the dB is locked down to prevent Users from changing values of certain cells which would result in an erroneous risk calculation. I'm not certain what you were looking at to conclude that some of the words are entered incorrectly. The example you provided seems appropriate to me as it is part of a calculation. Here's how the dB works.
There are three Modules: Screening. Risk Assessment. Background.
Generally, a User would start with the Screening Module, determine which compounds on their study property exceed the screening values and then proceed to the Risk module.
The idea is simple, but the execution is a nightmare due to the inability to sort the massive compound list or search by compound name. Searches can be done by the CAS number of a compound (the international recognition number)
, because many compounds have multiple synonyms. It become extremely frustrating when you have to re-enter the same data four times (minimum to get through the Risk module.