Unable to load Purchase order after fresh install of FMS

[tosca925]

We have jsut done a fresh install of FMS on a couple of workstations after doing this we are having problems with odering.

 

When they try to add an order they get a 'Fatal Error' Unable to load purchase order proceesing?

 

 

Does anyone know what is the problem with this?

[DMcCoy]

What's the exact error? There is one that shows up since the move to 2005 that looks terrible when all it really means is the cost center has no money left in it

[tosca925]

Fatal Error' Unable to load purchase order proceesing

 

Tis is all iget and when i click on Ok i get the purple hand.

[DMcCoy]

Capita KB

 

KB1431 - Fatal error unable to load Purchase Order Processing

Created 29/05/2002

Last Updated 15/11/2007

Affected Products FMS

Notes

Fatal error unable to load Purchase Order Processing

Borland database engine communication error directory controlled by other net file

The user is unable to go into Order/Invoice Processing until their colleague exits.

Advice

We understand that this situation generally occurs if the user does not have permissions to the LOCKDIR directory containing the PDOXUSRS.NET file.

 

If the FMS program files are installed locally on each workstation:

 

1. Alter the Net DIR within the BDE 32 configuration on each networked machine. This will enable the BDE to access to the temporary files.

2. Find the BDE Administrator (Start|Settings|Control Panel|BDE administrator)

3. Go to the Configuration Tab.

4. On the tree on the left hand side, select the Configuration|Drivers|Native|Paradox

5. Set NET DIR to the Drive letter and lock directory where the Finance.exe resides i.e. C:\LOCKDIR

6. C:\LOCKDIR should be created before any orders are added or edited by the user on their workstation, the user must have permission to create and write to this local directory.

7. On the tree go into Configuration|System|Init

Set LOCAL SHARE to FALSE.

 

If the FMS Program files are installed centrally on a networked Drive, i.e. the Finance.exe is shared out from the server, then please ensure that the following settings are in place:

 

1. Alter the Net DIR within the BDE 32 configuration on each networked machine.This will enable the BDE to control sharing of the temporary files.

2. Find the BDE Administrator Start | Settings | Control Panel.

3. Go to the Configuration Tab.

4. On the tree on the left hand side, select Configuration|Drivers |Native |Paradox Set the Net Dir to the Shared Drive letter and lock directory where the Finance.exe is shared from the server S:\LOCKDIR

 

(Please Note that the users must have access to the lock directory on the networked drive)

 

On the tree go into Configuration|System|INIT

Set local share to TRUE.

 

This can only be caused by the Netdir either not being in a shared location or the user not having access to the location in which it is being held.

[tosca925]

Excellent DMcoy.

 

 

Sorted my problem instantly. Thanks very much

[domw]

After hours of trying by myself I find an 8 year old forum thread that just happens to exactly describe and fix my issue. Cheers!

[Debbie99]

A Thank You from me as well. It fixed our issue.

[Jawloms]

Thank you. I just had this problem 13 years later and this fixed it!

[TwistedHelixis]

Just had this issue on our one FMS computer (primary school)

 

2. Find the BDE Administrator (Start|Settings|Control Panel|BDE administrator)

3. Go to the Configuration Tab.

4. On the tree on the left hand side, select the Configuration|Drivers|Native|Paradox

5. Set NET DIR to the Drive letter and lock directory where the Finance.exe resides i.e. C:\LOCKDIR

 

Currently this is set to c:\programdata\fms, do I need to change this location.

 

We dont have a c:\LOCKDIR folder

Edited May 10, 2021 by TwistedHelixis

[Jawloms]

I think essentially it doesn't matter where it points to, so long as the location it is pointing to exists and the user trying to use FMS has full control over it.

[TwistedHelixis]

Ended up deleting the users Windows login profile, when they logged in with a new profile all was good with FMS :0)