The Fixed Assets data file FASSD.DMD gets created (or overwrites the existing file) every time any of the reports 1 to 4 are printed. That would be the Asset Report, the Depreciation Projection Report, the Depreciation Comparison report, and the Asset Net Value report. If anything is preventing the FASSD.DMD file from being created, that would result in the error message you are getting.

Has this report been printed OK before and just stopped working now? Or has this never worked? If the first, then have you changed anything or installed anything new?

Check that the user who is logged in and using Fixed Assets has full read/write access to the F: network drive, and specifically the F:\ASP\DATA directory. This would be a network setup process. Also determine if the FASSD file is marked as read-only; it should not be.

What you could do is try to rename the FASSD data file, then print the report. When I did this, the FASSD file is simply recreated.

Neither printing any or the general reports or editing assets uses the FASSD file; those functions would therefore not trigger the error you are getting. Make sure also the version of the Windowing System Manager and if security is enabled.

Regards,
Softrak Support

(edited for typos)

[This message has been edited by Softrak Support (edited 04-27-2001).]

Were you able to print these reports prior to upgrading to the new version of Novell?

We have had similar errors reported on other applications after having upgraded to a newer version of Novell or Client 32 in that certain reports and/or exports no longer worked and would display:

"Cannot open F:\ASP\DATA\.dat" or
"File Unit 5 is not open".

In those instances, other ACCPAC modules worked just fine, but it was our Quik Reports that was complaining.

To determine if this is indeed network related, put a copy of your FA data onto your local hard drive, then create a new WSM Start List item for the directory where you copied the data to. Try to run the report - does it work?

If so, it could be the newer version of your Novell that is causing the problems with this older version of Fixed Assets. You could go back to the earlier version of Novell that you were running and see if this clears it up on your Server data.

Before doing this however, you may want to just try re-installing the WSM6.5. Sometimes, this has been known to resolve errors such as this.

Please let us know your progress.

Regards,