K
Keith
Hello all,
Given - I understand the question I have - has more to do
with user training than another solution - but I was
wondering if some people could throw some ideas out.
When a user single clicks on a CAB file - it attempts to
install it on their PPC - and then the file is removed off
of their PPC. However, if a user clicks and holds down on
the file - one of the options presented is to beam the
file.
I'm just curious - is there any way to make the CAB file
read only - so that they can only beam and not install?
Or is there a different way to beam over the application -
perhaps from another menu I'm not seeing (dare I say -
like Palms - sorry).
Or is there a way that if the user accidently single
clicks on the file and says - yes install (instead of
beam) that the file would NOT remove itself after the
install/upgrade?
Again - I know I'm asking for something that the users
should "know" or be trained on - but what happens in
the "real world" vs. reality - are often 2 very different
things.
thank you.
Given - I understand the question I have - has more to do
with user training than another solution - but I was
wondering if some people could throw some ideas out.
When a user single clicks on a CAB file - it attempts to
install it on their PPC - and then the file is removed off
of their PPC. However, if a user clicks and holds down on
the file - one of the options presented is to beam the
file.
I'm just curious - is there any way to make the CAB file
read only - so that they can only beam and not install?
Or is there a different way to beam over the application -
perhaps from another menu I'm not seeing (dare I say -
like Palms - sorry).
Or is there a way that if the user accidently single
clicks on the file and says - yes install (instead of
beam) that the file would NOT remove itself after the
install/upgrade?
Again - I know I'm asking for something that the users
should "know" or be trained on - but what happens in
the "real world" vs. reality - are often 2 very different
things.
thank you.