My attitude is that, if a solution to an Outlook issue is available, I will
provide as much of that solution as I know and have time to give. The
solution I gave is the simplest one for the issue you presented. If you find
the solution too difficult (and I would not consider this a difficult
solution at all, not compared with some of the more intractable Outlook
development challenges), you're certainly entitled to redefine the issue so
that it might be amenable to an easier solution. We all make adjustments
like that all the time.
But we can't read your mind. If you want other solutions, you have to tell
us where you're willing to compromise. Note in particular that the subject
of your post included the word "security," which is something that gets
serious treatment in any computer programming discussion forum, including
this one. It carries an assumption that you want a solution that a user
cannot easily undo. A change in the view settings does not meet that
security test. I would have been less than "helpful" if I had failed to
point that out.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54
"Netty" <(E-Mail Removed)> wrote in message
news:750D79CA-6497-4B45-B911-(E-Mail Removed)...
> Yes, that's true - but sometimes the easiest answer is nice to see too.
> Everything I've seen you post is all complicated and with an attitude. If
> you want to help people - start acting like it. Not everything has to be
> so
> difficult.
>
> "Sue Mosher [MVP]" wrote:
>
>> The user can, of course, turn it back on or apply a different view.
>>
>> "Netty" <(E-Mail Removed)> wrote in message
>> news:E31D83FE-4108-4E81-B15D-(E-Mail Removed)...
>> > Or even easier I found is going into Other settings and not selecting
>> > the
>> > "allow in-cell editing". Perfect and EASY.
>> >
>> > "Sue Mosher [MVP]" wrote:
>> >
>> >> You can adapt the technique shown in the code sample at
>> >> http://www.outlookcode.com/codedetail.aspx?id=778: Put code behind the
>> >> form
>> >> to set a variable's value when the item is opened, and allow changes
>> >> if
>> >> that
>> >> variable is set to the proper value.
>> >>
>> >> "Netty" <(E-Mail Removed)> wrote in message
>> >> news:481A1795-D503-4ED9-88D6-(E-Mail Removed)...
>> >> >I have created a custom Task form and have it displayed by fields in
>> >> >a
>> >> >folder
>> >> > under Tasks. Several fields are the yes/no icons which can easily
>> >> > be
>> >> > clicked
>> >> > on. I want to know if there's a way to make those read-only on the
>> >> > task
>> >> > view
>> >> > (so they can't be checked or unchecked) and then once the user opens
>> >> > the
>> >> > form
>> >> > by double-clicking, then the field can be updated (checked or
>> >> > unchecked).
>> >> > Anyone know if this is possible?
Similar Threads
