What about just automating Outlook?
--- On Wed, 10/1/08, Jack Skelley <[EMAIL PROTECTED]> wrote: > From: Jack Skelley <[EMAIL PROTECTED]> > Subject: RE: Disable Mouse When A Form Is Visible > To: "profox@leafe.com" <profox@leafe.com> > Date: Wednesday, October 1, 2008, 4:19 PM > Paul: > Warning my users would make them want to mess it up all the > more! I love these guys but all have been hit in the head > with sticks and pucks their entire life. > You are absolutely correct about the fragile application. > I tried using CDO to send email to our exchange server but > the mail was rejected. Plus I have tried too many other ways > to send mail that doesn't work either. > What does work is to launch the web access version of the > exchange box and send mail that way. But it involves > multiple windows that are touchy as to what window is > getting the info. Especially when attachment windows appear. > I tried making the window hidden but then the data transfer > does not take place. Apparently the window must be on top to > receive the data. > Thanks for the suggestions. > Regards, > > Jack > > > ________________________________________ > From: [EMAIL PROTECTED] > [EMAIL PROTECTED] On Behalf Of Paul McNett > [EMAIL PROTECTED] > Sent: Wednesday, October 01, 2008 3:01 PM > To: [EMAIL PROTECTED] > Subject: Re: Disable Mouse When A Form Is Visible > > Jack Skelley wrote: > > This is what modal is for when you have a pure VFP > app. But in my case this is not true. There are other open > apps that VFP is 'talking to' as long as the current > window doesn't change all is good. But if user activates > another window and I am trying to load window 'x' > and window 'y' becomes active all quickly goes down > hill. > > I am sure that my users do not know alt+tab as a kbd > shortcut... > > Ok on the message box idea. > > Thanks for any ideas you have. > > If a mouse gets an electric shock when it grabs food from > slot b, it > learns to grab food from slot a instead. > > So if really bad things happen if a user doesn't wait > for a process to > finish, why not warn them with a message box and then if > they forget, > that really bad thing will happen which will keep them from > doing it > again in the future. > > But I'd go back to the source of the problem. What > about the design is > so fragile that it can't stand user interaction? > I'd fix that design > problem instead of the symptom. So for instance, if you are > interacting > with an IE window and it would be bad for the user to close > that window > or pull up a different web page, you could disable it or > make it > invisible for the critical time of the process. Or > something. > > Paul > > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
