Hi Aparna, I actually changed around the file so that instead of the calculation being on the report side, it is entered in input (or auto calculated in excel and imported). This actually works better because we can scan through the database and see thickness without have to create a log or calculate manually. Strangely, there are still funny things going on with the decimals, though they are no longer an issue. Sometimes when I import thickness data a number such as 10.5 may display as 10.49999999 in the lithology table. Again, not an issue because on the report I have thickness formatted to 0.0
↧