Farzad et al. --
If your project database reaches 2GB, the editing capabilities can fail and cause data loss, I think. The only solution is to "compact and repair" the database occasionally before you reach this limit. It's a good idea to make a copy of the project database (or at least critical tables) around just in case things like this happen.
I believe I got this same error last week. I had spent 4 hours carefully modifying management operations in selected HRUs, using ArcSWAT's "edit subbasins" dialog boxes -- when suddenly the process stopped and could no longer find the mgt2 table. During all these edits, the project database had grown huge and had just reached the 2GB limit. I repaired and compacted the database (which reduced its size by about 90%), but I had lost the mgt2 table and all my work. I had a copy of mgt2 from other model runs, so it wasn't a catastrophe, but it was still frustrating.
Remember, a Jedi faces each set-back with calm resolution...
Cheers,
-- Jim
From: "farzad emami" <
farza...@gmail.com>
To: "ArcSWAT" <
arc...@googlegroups.com>
Sent: Thursday, December 17, 2015 6:57:04 PM
Subject: [ArcSWAT:7782] Error in edit Subasins Input step (the microsoft access database engine cannot find the input table or query)