Open jsfried opened 2 months ago
Unfortunately this relates to setting the damage codes on the newer workflow that customizes FVS_TREEINIT_COND. This step needs to get some information out of master.tree so we need to use the ado which means we are subject to the 2GB size limitation. The plan is for @druepdx to work on the FVSIn tables creation as part of the next round of SQLite conversions. This is an issue to keep in mind as we decide how much of the old workflow to keep intact.
So it isn't just the DAO that is problematic? ADO is too? In terms of random errors?
This isn't a random error. The size of the query result exceeds 2GB so the ADO can't work with it. It's the same error Cat and I ran into trying to build the FVS_InForest tree table for the CWI project. The number of records in master.tree determines whether or not you hit this. Once master.tree is in SQLite we don't have to use the ADO any more and are no longer constrained by the 2GB limit.
Performing a workflow involving 6 variants across two states (OR and WA). Needing to build FVSIn.DB files for each variant. Built project with PLT_CN list from two states. Connected to OR FIADB and got all 6 FVSIn.DBs built. Went to add WA FIADB and got FVSIn built fine for the first 5 variants with no difficulty. For WC (which does have a lot of plots), we got this error dialog:
Tried re-running the FVSIn.DB build process with WA overwriting existing values and with OR overwriting existing values. Neither one worked (same error). After deleting the failed FVSIn.DB, I was able to connect to WA FIADB data and build that state's FVSIn for WC; then renamed the DB and built an OR FVSIn for WC. So I did find a workaround, but this is not nice behavior. Am wondering if the error relates to something in the old (Access) workflow and if so, couild we have a switch that turns the Access database producing workflow off so that we can get a unified multi-state FVSIn for a variant. @lbross @druepdx