NewsArchive
03-12-2014, 02:44 AM
Hi All
I think that I am losing my mind.
I have an SB7 install set that has, to be expected, working flawlessly at
all client sites for years [even before SB7] - well over ten years. It is a
very simple setup with the target folder [call it release] specified by the
person installing. Binaries are extracted into that folder. The file
attributes are always archive and we have our own program, written in
Clarion, that will copy these files onto the workstation. The person logged
in and running the program on the workstation always has full rights to copy
from the release folder onto a folder on the workstation. This is done by
running our little program. It is a simple copy exercise. The only issue
has ever been inadequate permission to copy from and copy to. Now here is
the thing. One client runs the setup and extracts the binaries into the
release folder and the permissions, not attributes, for only some of the
files changes from full rights to copy to no rights to copy. I am going to
the client to try this for myself but just want to make sure that there is
nothing in SB that I need to look out for. I am guessing that something
went wrong with MS retaining the full rights to some of the binaries and it
is unrelated to the action of installing the latest binaries with SB. Just
wanting to make sure.
Any ideas?
BTW - the consultant techie for this client fixed the problem with me
present - I watched him. It was a lack of permission to copy certain files.
Cheers
Andre
I think that I am losing my mind.
I have an SB7 install set that has, to be expected, working flawlessly at
all client sites for years [even before SB7] - well over ten years. It is a
very simple setup with the target folder [call it release] specified by the
person installing. Binaries are extracted into that folder. The file
attributes are always archive and we have our own program, written in
Clarion, that will copy these files onto the workstation. The person logged
in and running the program on the workstation always has full rights to copy
from the release folder onto a folder on the workstation. This is done by
running our little program. It is a simple copy exercise. The only issue
has ever been inadequate permission to copy from and copy to. Now here is
the thing. One client runs the setup and extracts the binaries into the
release folder and the permissions, not attributes, for only some of the
files changes from full rights to copy to no rights to copy. I am going to
the client to try this for myself but just want to make sure that there is
nothing in SB that I need to look out for. I am guessing that something
went wrong with MS retaining the full rights to some of the binaries and it
is unrelated to the action of installing the latest binaries with SB. Just
wanting to make sure.
Any ideas?
BTW - the consultant techie for this client fixed the problem with me
present - I watched him. It was a lack of permission to copy certain files.
Cheers
Andre