Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Multiple procedures vs. one procedure - revisited
Message
 
 
À
10/06/2005 14:07:47
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Database:
Visual FoxPro
Divers
Thread ID:
01022173
Message ID:
01022283
Vues:
11
This is what we currently have in SET PROCEDURE:

C:\MMORTALS\COMMON30\PROGS\UTILITY.FXP, C:\MMORTALS\COMMON30\PROGS\MOVER.FXP, C:\MMORTALS\COMMON30\PROGS\SETUP.FXP, C:\MMVISCOLLECT\PROGS\MAIN.FXP, C:\MMORTALS\COMMON30\PROGS\VFPXTAB.FXP, C:\MMVISCOLLECT\PROGS\VIEWS.FXP, C:\MMORTALS\COMMON30\LIBS\CACTX.FXP, C:\MMORTALS\COMMON30\PROGS\RS2DBF.FXP, C:\MMORTALS\COMMON30\PROGS\DBF2RS.FXP, C:\MMORTALS\COMMON30\PROGS\DBF2XML.FXP, C:\MMORTALS\COMMON30\PROGS\XML2DBF.FXP, C:\MMORTALS\COMMON30\LIBS\CSESSION.FXP, C:\MMORTALS\COMMON30\LIBS\MSGSVC.FXP, C:\MMVISCOLLECT\PROGS\PHI_COLLECTION.FXP, C:\FF605\PROGRAMS\FFNEWOBJ.FXP, C:\MMVISCOLLECT\PROGS\FFVISC_UTILS.FXP, C:\MMVISCOLLECT\PROGS\ASSIGN_QUEUES.FXP, C:\MMVISCOLLECT\PROGS\VISCOLLECT_CURSORS.FXP, C:\MMVISCOLLECT\PROGS\VISCOLLECT_OTHERS.FXP, C:\MMVISCOLLECT\PROGS\VISCOLLECT_UTILITY.FXP, C:\MMVISCOLLECT\CAREMOTE\CA_QUICKSEARCH_R.FXP, C:\MMVISCOLLECT\CALOCAL\CA_QUICKSEARCH.FXP, C:\MMVISCOLLECT\CALOCAL\CA_SCHEDULED_LETTERS.FXP, C:\MMVISCOLLECT\CAREMOTE\CA_SCHEDULED_LETTERS_R.FXP, C:\MMVISCOLLECT\PROGS\ACTIONS_CURSORS.FXP, C:\MMVISCOLLECT\PROGS\LETTERS_CURSORS.FXP, C:\MMVISCOLLECT\PROGS\INSURANCES_CURSORS.FXP, C:\MMVISCOLLECT\PROGS\TQM_CURSORS.FXP


My functions for one particular form are in the last function and I see a performance degradation. What should I do?

Thanks.


>>Everything added to set procedure list! Order is important, worse having multiple procedures open at same time there is no way to call a procedure from one of them selectively (I don't know at least - unless you use "do ... in ..." ). You better use classes.
>
>But the class definitions are searched along the same set proc list <g>...
>Clean coding practices or high attention are necessary when dealing whith duplicate names,
>regardless of them being class names or function names.
>
>But it is a nice dirty way to overwrite functions if you know what you are doing
>
>regards
>
>thomas
If it's not broken, fix it until it is.


My Blog
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform