Losing changes in DMS

Cross your fingers and click your heels, because the worst part I have found is it tends to be the same file time & again (maybe a corrupt temp file problem.) This used to be only a network stability issue at our office, but the newer versions of DMS seem capable of causing them on their own.

If it fails twice, two-step it (save elsewhere and re-import) and be glad none of the other files are affected. Anything coming from the conduit, printed normally, or imported into the database will be just fine (and importing over an existing file does not clear the categories *glares at re-printing*)

We had this issue. We ran a database maintenance job on it, and it seemed to have eliminated the issue. Knocking on wood while crossing my fingers and clicking my heals. You are right, it was a very sporadic issue.

Any chance you are running Symantec/Norton AV software?

Yes. We went to Endpoint (v11 from v10) back in December, but the problem did not get bad until a month or two later.

Well regardless of AV software (my opinion, based on personal experience) there are some things to consider. One is that even though Mr. Norton may be gone, his database corruption may have lingered. Second, if the other software is performing real-time scans on the database, two issues may arise: one is that it WILL dramatically hinder performance, and it CAN possibly corrupt the database by scanning files while the program is trying to write to them. At a minimum, I would recommend EXCLUDING and LACERTE and DMS database files from these scans. Once this has been accomplished (call tech if you need to), run the DBRepair (provided you are not on Vista because you will need to submit a DNA sample to Bill Gates first) and get the database back in order. There are people at tech that can help - I have seen the results and was impressed. It pains me when I see folks having a bad time with a product that IS solid and dependable, when other software is not hammering it all day.

Bill

I have a question to add to this... what program are you using for your worksheets?  We have this problem when we use Microsoft Excel 2007, but not Microsoft Excel 2003.