Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Sql not always rushmore'd
Message
 
 
À
04/05/2006 11:15:27
Mike Yearwood
Toronto, Ontario, Canada
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
01113886
Message ID:
01119213
Vues:
28
>>>>I'm not seeing output from this test program on the screen, but my main program shows it on the screen. The main program is actually from Mere Mortals framework.
>>>>
>>>>I'm wondering, if MM users can reproduce this behavior.
>>>
>>>Perhaps MM turns sys(3092) and sys(3054) off during startup?
>>
>>I searched our project using Code Reference and there is no SYS(3054 in it.
>>
>>But here is very simple reproducible scenario:
>>
>>Create a program
>>with the following lines
>>private pcInfo
>>
>>SYS(3092, "SQLLog.TXT")
>>sys(3054,12,"pcInfo")
>>*some select statement
>>
>>Then run any select statement in the command window. You'll see output displayed on the screen. That's what happenning here.
>
>Ah! Well, just augment the SQLThermo thing I did and use it for every query. Then you won't get any output at all and you can direct all query output to a file by changing a single class.

Sounds like a good idea. E.g. I can add a property to your class lGatherStatistics and depending on this property turn on the sys(3054). The problem, though, that I don't use your class every time when I run query.

Also do you know if applying SYS(3054) slows things? Probably it would not be even noticable...
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