Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Form's datasession can't be released
Message
 
 
À
16/01/2002 17:55:06
Information générale
Forum:
Visual FoxPro
Catégorie:
Gestionnaire d'écran & Écrans
Divers
Thread ID:
00605724
Message ID:
00605867
Vues:
23
Did you release oWord and aPropChar in Form's Destroy?

>No prob.
>
>The code is:
>
>
>dimension apropchar(5,2)
>oword = createobject("word.application")
>with oword
>    apropchar(1,1) = ".Application.UserName"
>    apropchar(2,1) = ".Application.UserInitials"
>    apropchar(3,1) = ".Application.UserAddress"
>    apropchar(4,1) = ".Activedocument.Password"
>    apropchar(5,1) = ".Activedocument.WritePassword"
>    for i = 1 to 5
>        if  type(apropchar(m.i,1)) # "U"
>            apropchar(m.i,2) = evaluate(apropchar(m.i,1))
>        endif
>    next
>endwith
>
>The code is fine and everything works, Claudio. But it isn't the point. I just try to say about a Type() function wich causes a memory hole or something. The objective of this code is to determine some Word properties and hold them. The property oword.activedocument.password if not set, will become undefined. Removing the password property test, the problem with datasession will not occurs.
>
>Btw, there is NO runtime errors.
>
>Thanks for your attention.
>
>Fábio
>
>>Fabio
>>
>>>
>>>
apropchar(1,1) = ".Application.UserName"
>>>apropchar(?,1) = "...
>>>
>>>for i = 1 to ?
>>>    if  type(aWordpropchar(m.i,1)) # "U"
>>>...
>>>
>>
>>If we analyze just that piece that you publ. here there is a dot at the first line (before appication) that looks weird for me.
>>
>>Like the first code that you publ. hardly had anything in common with this here.
>>
>>Can you publ. the whole code ?
>>
>>
>>Claudio
If it's not broken, fix it until it is.


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

Click here to load this message in the networking platform