wooooooo, slow down brother, I don't know if your to smart for me or I am to smart for you, but I am having a hard time understanding the jist of your message, but I am at work so I am kinda brain dead

I will take another look at it as soon as I get a few minutes

>>ok
>>
>>First during every forms load event if I run a sql I set talk on to see the sql meter, I was getting the "memory low, streaming output" error I did a quick fix for that
>>

>>lcUniqueWindowName = SYS(2015)
>>DEFINE WINDOW (lcUniqueWindowName) FROM 0,0 TO 1,1
>>SET TALK WINDOW(lcUniqueWindowName)
>>SET TALK ON
>>

>>
>>second what will this do?? Inkey(0.1)
>>
>>Third I never printed before seeing the error, just load and goto the error
>>
>>Granted I do have a lot of vars on some of my forms, but not one where I get the error (i get it on 2 forms) on the second I have a lot of objects
>>
>>and I alway do a release lc_name, lc_name2, varlist, on the release of every form
>
>So Stephen, I guess I am somehow near, since your are (where) able to get this error which IMO is very rare (guys, is it ??).
>
>The question about printing was just about my questioning whether your printing (which you don't) may imply illegal stuff, even if you didn't get the message. Never mind for now.
>
>Maybe you think that I think that somehow too much memory is used. Well, I do not at all; I just assume that somwhere an illegal operation is performed (can you explain the Memory low message ? I can't since it really can't due the virtual memory once that's enough and which I won't question).
>
>So, now let's work on this bugger ...
>
>I wonder, do you have any OCX on board ? I mean, I don't know of any which just does work by itself; it always needs some workaround somewhere. Mind you (all disagreeing) our app does that many operations in order to have a form loaded that I can't understand why things work at all. I mean, we really stress things, and at some subjects this is noticable. But never mind this.
>
>My Inkey(0.1) (or Wait Windows) forces "the" (??) other thread to get a timeslice, and it's just this which may stop VPF's internal operations on a thread to stop at the wrong moment and never get alive again. So, I just wonder whether this may be your problem, and you really should test this.
>Anyhow, at the moment (since yopur reply) I guess this isn't it and think more of the memory low thing. Mind you, once this once's there, it starts to have to do with taskbar-stuff, and now look at your Set Talk ...
>Again, I just recognize the exact same behaviour, and the fact that you (now) don't receive this message, doesn't imply that you won't have the problem. My situation was IMO just recognized by VFP so it could give the message, but since it's a warning *and* things go wrong anyhow, for me this says you might just not get the message and the rest is the same.
>
>In order to get not too much in trouble I really should try the Inkey first because it's the most easy ... as long as you know where to put it, and that's hard. For me the most obvious is that you interupt somehow an Activate which must then be triggered by some parallell process like a Toolbar or a Timer;
>It takes too much explaining for now, but I hope you can think of where to put this Inkey now. F.e. if a Timer Activates a Form (i.e. Show()), put it in the Timer after this activation. If this doesn't help, or this isn't it, or you are at the wrong place. So please try to understand what may be happening : some process get's interrupted and won't go alive again. An Inkey or Wait Window in the other process, gives it's timeslice away to the waiting process.
>
>Curious ...