Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Handling non expected results
Message
De
27/11/2001 12:28:10
Alexandre Palma
Harms Software, Inc.
Alverca, Portugal
 
 
À
27/11/2001 12:23:14
Information générale
Forum:
Visual FoxPro
Catégorie:
Web Services
Divers
Thread ID:
00586062
Message ID:
00586435
Vues:
16
>>Hi Michel here goes my opinion
>>On scenario 2 / 4 I will use COMRETURNERROR since I whant to state that an exception has occurred e.g. validation failed or an error as occured the explanation message is what you put on the comreturnerror.
>>On scenario 3 I will return an empty string since everything is OK but no data has match my criteria.
>
>Good for point 2 and 4.
>
>As for point 3, this will then force the client to implement the logic of verifying for an empty string before converting to a cursor. But, for that one, it is as good as the other approach. I was mostly looking for point 2 and 4. Thanks

Michel about point 3 if the client don't implement the check for empty he will get an error when trying to do an XMLTOCURSOR in this case the error routine will enter in the game.
Alexandre Palma
Senior Application Architect
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform