Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFPx+Ctl32+CodeBook Declare DDL call caused an exception
Message
De
15/09/2008 06:47:53
Lutz Scheffler (En ligne)
Lutz Scheffler Software Ingenieurbüro
Dresden, Allemagne
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows 2000 SP4
Network:
Windows 2008 Server
Database:
Visual FoxPro
Divers
Thread ID:
01347522
Message ID:
01347532
Vues:
22
Bahv,

then you need to figure out what is different beween your IDE and a non ide call. Try to use a vanilla IDE (maybe on a other comp.) Log the settings of your runtime (DISP STATUS; DISP MEMO) to some file and compare with the settings of your IDE, Do you use a included config.fpw? Check its settings.

What else? Check if the runtime dlls match does of the ide. VFP uses different dlls if you run the IDE or start the Exe from Explorer. Check that there is no mismatch with SP2 or VFP 9

Agnes
>Hi Agnes
>
>>Why can't you debug the exe? If you compile the exe with debuginfo on on run it from VFP's commandline it should be no problem. Does it make a difference if you run the exe from ide or from explorer?
>
>Thanks, I tried it this way and the error does not happen. I have DO myexename.exe from the command prompt and it works just as fine as if I did a DO main.prg.
Words are given to man to enable him to conceal his true feelings.
Charles Maurice de Talleyrand-Périgord

Weeks of programming can save you hours of planning.

Off

There is no place like [::1]
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform