Falimit.dat error in 9.0

[aryya]

I work in a small company that uses Peachtree Complete Accounting setup on a network. Originally we only had one user, but a few months back we ordered two more licenses and upgraded from 8.0 to 9.0. The clients were installed as a network install. However, I was not an employee when that happened so I don't have anymore specifics on that.

Anyway, the problem we're getting is when a user wants to access Peachtree Fixed Assets. The error we get when attempting to access the fixed assets database is that peachtree couldn't find "Falimit.dat" and to either re-install Peachtree or update your tax tables. I've re-installed Peachtree to no avail and I'm fairly sure I don't need to update my tax tables. Could this have something to do with too many users trying to access the fixed assets database? Could the licenses not be installed correctly?

There is one user who has never had any problems at all w/ his Peachtree, including accessing the Fixed Assets Database. I went to his computer to search for the Falimit.dat file with the hopes that I might be able to copy it to the malfunctioning PC. I found it on his C drive in 2 places, one of which was in his BCS directory. However, when I went back to the original computer that was having the problem there was no BCS directory at all!

Signed,

Confused in maryland

Since our Peachtree was as a stand-alone application and then u

O

[has@bdssr.com]

I just dealt with this. The problem is almost certainly in the drive mapping of the non-host machines. You need to map from Windows to X:\ (the drive which holds the data), then change the DATAPATH entry in your pcw90.ini file to X:\peachw. I never had a problem with this until I upgraded to 9.0

[asconsult]

I have also had difficulty with this and tried the suggestions you listed. Our host drive is F: with a mapping on the user's computer to F. With the Datapath pointed to F:\peachw, we can access PCA, but not Fixed Assets. We get the same error message (can't find falimit.dat). If we point the path to c:\peachw, we can use Fixed Assets, but not PCA.

The installation was originally done with the paths pointing to F:. Appreciate any light you can shed on this.

BS

[has@bdssr.com]

That's a different setup from what I have - I have the program on my c:\ drive and I'm wondering if that's part of the problem. pcw90.ini resides in my Win 2K WINNT directory on the c:\ drive as well, and I'm wondering if this problem with FA (which I never had a problem with until upgrading) gets confused with anything other than a standard configuration - meaning the ini fle should be on the same drive as the program file (you'd think this shouldn't be an issue, but who knows). I'd try flipping the program and data to the c:\ drive if you have the room (or maybe make the room; nonnetwork programs such as Excel have no problems on other drives), remap the works and go from there.

[Jacky Tse]

The problem is caused by a mapping that makes the data path of Peachtree becomes the root. For example, in the computer that serves as server ( that's with Peachtree data ), the data should be located in a folder like:

c:\data\peachw

instead of c:\peachw

As a result, you can map c:\data as other stations' f:. Then, other stations' f: is point to the servers' c:\data instead of point to c:\peachw. In this way, fix asset should work properly.

Reference:
Fix Asset Problem (http://www.peachtreeusers.com/.forums/showthread.php3?threadid=789&highlight=asset)