permission problems with filepro application

[Lerebours, Jose]

Howdy!

I came across an application set to 777 for all filePro
files.  Not good, I said. I ran 'serperms' but this in
turn, messed things up.

As operators started to work, the lockfile was being
created with 600 mode by first user that hit the file;
every user there after will get a "permission denied"
error.

The lockfile is also owned by this operator, not filepro.
This lead me to believe that binaries are not UIDing
to filepro as they are executed.  Comments?

Not wanting to waste any time on this and not being
able to keep operation off, I used already provided
shell script to reset permissions, which in turn set
all files to 777, removed lock flies and all was well.

Questions:
1. Why is this?
2. What is the file that holds the list of permissions
   which is used by setperm?
3. What should the permission for *clerk & *report be?
4. Suggested course of action?

Running on SCO 5.0.6 - filePro 4.5 ...

Regards;


--
Jose Lerebours


PS:  Please cc  me on all messages as I unsubscribed and
have not been able to resubscribe - I have sent request
a couple of times via email and via 
http://mailman.celestial.com/mailman/listinfo/filepro-list

I was getting two copies, I unsubscribed and now, I cannot
resubscribe at all.

Thanks!