Steve-
Yep, that worked well for the decimal point adjustment.
The second question; I will try to explain a little better.
Basically in ArcView GIS I overlay all of the different attributes (Yield,
Soil Type, Fertility, Management Practices, Crop Type, etc.) and the sofware
divides the fields into 60 ft square cells, and populates those cells by
looking at the infomation that is layed on top of those cells. It is the only
way to combine non-uniform spatial data into one database for querying.
The next step is to combine multiple fields database's into one so it then
becomes one large anonomous databse that all producers can use to benefit
their operation. So what I then have is one large database with thousands and
thousands (500,000 +) records. When I combine these tables from multiple farm
fields, if one farm field's database does not have a phosphorus populated
field in it's database, access automatically assigns 0's for those cells. So
when I run a query to get the average phosphorus of the complete database,
those 0's throw off the average of what the actual is.
So I more less need to find a way for access to recognize a "0" and
automatically create a null value for those cells. There should never, in any
circumstance, be a "0" in any part of this database.
The only thought I had was in my queries to always have to say Soil P >0
blah blah blah.
Does that help? Thanks again for your help and tips!
Bryan
"Steve Schapel" wrote:
> Bryan wrote:
>
> > 1) Some of my numerical fields come into access with a lot of decimal places
> > that are not necessary. Since it is a linked database, access will not let me
> > limit the number of decimal places in the design view of the table. So now
> > when I create any reports or queries, I get a pH value, for example, that is
> > 7.3267546574 instead of just 7.3, which is plenty. It just makes the reports
> > look sloppy. Is there any remedy? I do not think I can efficiently limit the
> > decimal places in ArcView.
>
> There are a number of approaches that can be taken here, depending on
> the specific requirements. You could use the Round() function.
> However, in the example you gave, probably if you go to the properties
> of the textbox in design view of the report, and set the Format property
> to Fixed and the Decimal Places to 1, should do the trick.
>
> > 2) Is there a way to set a "null" value for any fields that are "0"? For
> > example, when I combine a table (In GIS) from one field that was soil sampled
> > for phosphorus with one that was not, those "P" cells for the field that was
> > not soil sampled become 0's in access, which totally throw off my queries.
>
> There will certainly be a way to handle it. However, I can't quite
> grasp exactly what you mean. Can you give an example with some sample
> data to illustrate what is happening?
>
> --
> Steve Schapel, Microsoft Access MVP
>
|