From: Keith G Hicks on 16 Feb 2010 22:47 I've looked into this and I find coding work arounds that I wouldn't expect would be needed after so many years of MS Access. You can do Debug.Print to put info in the immediate window but there doesn't seem to be anything like Debug.Clear. Well that just seems truly odd but typically microsoft so I figured I'd ask here to see if my findings are true. Thanks, Keith
From: AccessVandal via AccessMonster.com on 16 Feb 2010 23:07 There's nothing to clear, why do you need it? or do you mean to clear the immediate window? Keith G Hicks wrote: >I've looked into this and I find coding work arounds that I wouldn't expect >would be needed after so many years of MS Access. You can do Debug.Print to >put info in the immediate window but there doesn't seem to be anything like >Debug.Clear. Well that just seems truly odd but typically microsoft so I >figured I'd ask here to see if my findings are true. > >Thanks, > >Keith -- Please Rate the posting if helps you. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access/201002/1
From: Keith G Hicks on 16 Feb 2010 23:12 Please read the subject of my post. "AccessVandal via AccessMonster.com" <u18947(a)uwe> wrote in message news:a3c00f14952ed(a)uwe... > There's nothing to clear, why do you need it? or do you mean to clear the > immediate window? > > Keith G Hicks wrote: >>I've looked into this and I find coding work arounds that I wouldn't >>expect >>would be needed after so many years of MS Access. You can do Debug.Print >>to >>put info in the immediate window but there doesn't seem to be anything >>like >>Debug.Clear. Well that just seems truly odd but typically microsoft so I >>figured I'd ask here to see if my findings are true. >> >>Thanks, >> >>Keith > > -- > Please Rate the posting if helps you. > > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access/201002/1 >
From: AccessVandal via AccessMonster.com on 16 Feb 2010 23:28 In that case, no. But there were codes out there which I can't remember where that can clear the immediate window. I think MS have the consideration of beginners if they were to use "Debug. Clear" hidden somewhere in their code coming to complaint about missing print outs in the immediate window or complaint the "Debug.Print" does not work. Keith G Hicks wrote: >Please read the subject of my post. -- Please Rate the posting if helps you. Message posted via http://www.accessmonster.com
From: John W. Vinson on 16 Feb 2010 23:30
On Tue, 16 Feb 2010 22:47:51 -0500, "Keith G Hicks" <krh(a)comcast.net> wrote: >I've looked into this and I find coding work arounds that I wouldn't expect >would be needed after so many years of MS Access. You can do Debug.Print to >put info in the immediate window but there doesn't seem to be anything like >Debug.Clear. Well that just seems truly odd but typically microsoft so I >figured I'd ask here to see if my findings are true. > >Thanks, > >Keith > Ctrl-A Backspace works for me. It's a debug window, not a user interface - a bit of user hostility should be expected! <g> -- John W. Vinson [MVP] |