Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Alright already! I'm stumped
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Divers
Thread ID:
00541837
Message ID:
00542208
Vues:
22
>>>It was just a whild guess, especially knowing your love for foxtools :) So, you may ship foxtools with your project and include it explicitly. This probably will solve this problem.
>>
>>I don't know if it'll solve the original problem or not, but retrieving the path from the registry seems to have worked. Frankly, I never would've have thought about Foxtools being the cause (especially in view of the nature of the error). It certainly wasn't referenced in the method being called in the script or by the method that was called from there.
>>
>>Thanks,
>
>Not sure if it's the same thing, but I think that this one bit me before too. I had a COM server that used foxtools in a method that wasn't being called. IIRC, I moved the COM server to a new folder, forgot to move Foxtools, and the object wouldn't instanciate.

The really strange part of this is that, apparently, the object did instantiate. If it couldn't find the library, then it returned false (.F.) from the Init. However, the error occurred 7 lines into a method in that object.

Still this puzzle is only a distraction from the initial (and still unsolved) problem. I have a SWAG as to what may be causing that, and may post a question later in that regard.
George

Ubi caritas et amor, deus ibi est
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform