Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Instantiating Outlook through VFP 6.0
Message
From
09/05/2000 13:09:15
Jared Anderson
Marketing Support Solutions, Inc.
Forest, Virginia, United States
 
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Miscellaneous
Thread ID:
00367348
Message ID:
00367714
Views:
30
>If you want some "ammo" for upgrading, look at "What's New for Microsoft
>Outlook 2000 Developers" by Jim Groves. It's a technical article in the MSDN
>Library.

Thanks for the reference; this was VERY insightful, and I see a LOT of useful additions (plus ... it was nice, albeit somewhat disappointing, to get confirmation one way or the other of my suspicions of it being a 2000-only feature).

I'll definitely discuss this with my team, and we'll probably approach the clients ..... BUT, I don't know for sure how that will go.

In the meantime, I have been trying to figure out a way to launch Outlook from within FoxPro (if Outlook is not already running). It is not as simple as ONLY specifying what program to run, as the EXE is potentially in a different directory for each user's machine.

SO, using a registry-access class, I scan the registry for the Default Mail client (under HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail) ... if for each user, this is Outlook, great ... if not, then I guess it is best right now (using this approach) to launch the program they prefer anyway.

Once I get the value from this (e.g., "Microsoft Outlook"), I append so that what's getting passed in is HKEY_LOCAL_MACHINE\SOFTWARE\Clients\Mail\[default-client]\Shell\Open\Command

This gives me the full path (per machine) to the Mail Application. For example, on my machine I get back ' "C:\Program Files\Microsoft Office\Office\OUTLOOK.EXE" Outlook:Inbox '

Herein lies the next complication. I was hoping to avoid "wrapping" this execute inside a C++ program or a DLL or such, but the ! / RUN function does not like the quotes if I try to say '! "C:\Program Files...."

But if I take out the quotes, it will of course be invalid because of the spaces.

SO, long-story-short, does anyone know away around RUN's inability to 'palate' filepaths that contain quotes and/or spaces???

Thanks so much! You all have been very helpful, even if only to point me in the direction of further references! :)

Jared M Anderson
Interactive Data Systems, Inc.
janderson@idevgroup.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform