Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP7 SP1 - More Automation Woes with Word now!
Message
From
30/01/2002 14:31:03
 
 
To
30/01/2002 14:20:13
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00612757
Message ID:
00612968
Views:
33
Jim:

>Actually it was 8 Nov 2001...

It sure does feel like 5-6 months ago.

>The workaround for this is pretty simple, to add an = sign before the call to the Move method.

OK. You detailed this to me and I guess this re-statement is for everyone elses benefit. And thats OK too. However, why do you have to add an = to the front of the call to the move method? What does it do exactly? Why doesn't it work in the normal way like VFP6?

>Also, I don't see it listed anywhere in the SP1 fix list.

Well, correct me if i'm wrong but you confirmed it as a bug to me and said that it had been passed up the line. You stated at the time that part of the problem was that there was some problem with For Each(ing) where object references were being accessed and this was why the Move method wasn't working. This is in the fix list so I assume that this was relating to the problem that I had with Outlook?

If it isn't, then if the bug was passed up the line prior to the release of SP1, why didn't it get fixed (or does it not work like that?).

>See my other post, and send me through the RTF files directly and I will be glad to have a look!

Done it!

Best

-Gary
-=Gary
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform