By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,477 Members | 1,627 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,477 IT Pros & Developers. It's quick & easy.

A2K - limit on lines that can be printed in immediate window?

P: n/a
I'm just looping through some tables and printing the names to the immediate
window. I notice that I lose the first few after the code has run. If I
step through they do get printed intially. It's about 100 tables. Is the
immediate window limited to the number of lines it can display?

thanks
Martin
Jan 17 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
It's been a few years but I think it was around 190 lines in the buffer for
the Debug window in A2K. If you search GoogleGroups you will be able to find
the exact amount.

--

HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
"Deano" <de***@mailinator.com> wrote in message
news:43***********************@ptn-nntp-reader03.plus.net...
I'm just looping through some tables and printing the names to the
immediate
window. I notice that I lose the first few after the code has run. If I
step through they do get printed intially. It's about 100 tables. Is the
immediate window limited to the number of lines it can display?

thanks
Martin

Jan 17 '06 #2

P: n/a
acourse, you could just run a test...

Function howMuchIsTooMuch()
Dim intCount As Integer
For intCount = 500 To 1 Step -1
Debug.Print intCount
Next intCount
End Function

or I could...
it's 199.

Jeremy
--
Jeremy Wallace
Fund for the City of New York

Jan 17 '06 #3

P: n/a
"Deano" <de***@mailinator.com> wrote in message
news:43***********************@ptn-nntp-reader03.plus.net...
I'm just looping through some tables and printing the names to the
immediate
window. I notice that I lose the first few after the code has run. If I
step through they do get printed intially. It's about 100 tables. Is the
immediate window limited to the number of lines it can display?

thanks
Martin

Of course it wouldn't be too much coding to write your own version which
wrote to an external file. Just append a new line each time and you would
bypass the limitations of debug.print.
Jan 17 '06 #4

P: n/a
Sub txtprint(Optional v1, Optional v2, Optional v3, Optional v4, Optional
v5, Optional v6)
Dim ifile As Integer
Dim sfile As String

sfile = "c:\debug.txt"
ifile = FreeFile
Open sfile For Append As #ifile
If Not IsMissing(v1) Then Print #ifile, v1;
If Not IsMissing(v2) Then Print #ifile, , v2;
If Not IsMissing(v3) Then Print #ifile, , v3;
If Not IsMissing(v4) Then Print #ifile, , v4;
If Not IsMissing(v5) Then Print #ifile, , v5;
If Not IsMissing(v6) Then Print #ifile, , v6;
Print #ifile,
Close #ifile

End Sub
That runs a lot slower than debug.print because if flushes the
file on every line. To make it run faster, take out the open
and close lines, and run them seperately.

(david)

"Deano" <de***@mailinator.com> wrote in message
news:43***********************@ptn-nntp-reader03.plus.net...
I'm just looping through some tables and printing the names to the
immediate
window. I notice that I lose the first few after the code has run. If I
step through they do get printed intially. It's about 100 tables. Is the
immediate window limited to the number of lines it can display?

thanks
Martin

Jan 17 '06 #5

P: n/a
Or just make a query on msysobjects.

Jan 18 '06 #6

P: n/a
"Anthony England" <ae******@oops.co.uk> wrote in
news:dq**********@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com:
"Deano" <de***@mailinator.com> wrote in message
news:43***********************@ptn-nntp-reader03.plus.net...
I'm just looping through some tables and printing the names to
the immediate
window. I notice that I lose the first few after the code has
run. If I step through they do get printed intially. It's about
100 tables. Is the immediate window limited to the number of
lines it can display?


Of course it wouldn't be too much coding to write your own version
which wrote to an external file. Just append a new line each time
and you would bypass the limitations of debug.print.


Or to an unbound control on a form.

Or to a variable, and then display the variable in a control on a
form.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/
Jan 18 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.