Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
COM+ Application throws unspecified error
Message
 
À
16/07/2014 05:45:39
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows 7
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Web
Divers
Thread ID:
01603720
Message ID:
01603835
Vues:
46
>>>Good to hear. IMO, you should still use some type of error logging.
>>>
>>>>OK, I finally found the problem, my class is based on another class, both are in the project which I used to create the DLL, but... I did not realize that in the base class I am using another class that is in a PRG that was NOT on the project, I added it and not it works fine.
>>>>
>>>>Thanks Craig!
>>
>>I do, that base class is there just to do that, it has an Error and LogError procedures, but they did not get fired in this case, I checked the log and there was nothing there, maybe for the error was in the Init?
>
>The morale of the story: the error logger is the first thing to do in .init() :).

In hindsight, I should have used more try -catchs... but I wrote that crap more than 10 years ago! But the question is why Error does not fire? I did a test and it should, and I know that the Error procedure works, for I can see in the log past errors, but... now I am happy that everything works, and I spent too much time already with this issue, and I doubt we are going to need it again, as we are moving all our code to c# anyways.
"The five senses obstruct or deform the apprehension of reality."
Jorge L. Borges?

"Premature optimization is the root of all evil in programming."
Donald Knuth, repeating C. A. R. Hoare

"To die for a religion is easier than to live it absolutely"
Jorge L. Borges
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform