Send Immediate Window contents to form textbox.

[Tony]

Hello,

Using Access2000, WinNT.

Using the Immediate Window, I can view the results of my VBA code as
it performs operations/calculations on my data. Now that I have all
the bugs worked out, I want that same debug.print information sent to
a form so a user can see what is happening as the data is being
processed. How can I do that?

It's not so much that I want the Immediate Window to pop-up over my
form but rather getting the same data generated using the debug.print
statement into a scrollable text box on a form. This way a user can
see procedure calls, failure/success results, etc.. as they are
executed in the module.

Any ideas are greatly appreciated!
Tony

[Wayne Morgan]

Yes, for the items you currently have a Debug.Print statement, just set the
value of a textbox instead.

Example from the Immediate window:
Forms!Form22!Te xt0="Hi there"
Forms!Form22!Te xt0=Forms!Form2 2!Text0 & vbCrLf & "Hi there again"

You could use "Me." instead of "Forms!Form 22" if appropriate. You may also
want to play with the SelStart and SelSelect properties of the textbox. Set
the textbox's Scrollbar property to Vertical and the Locked property to Yes.
If you leave Enabled set to Yes, the user will be able to select the text
and copy it for pasting elsewhere. If you set the Enabled Property to No,
the user won't be able to do anything but read the text. Setting Enabled to
No will also disable the scroll bar.

--
Wayne Morgan
MS Access MVP
"Tony" <hs*********@ya hoo.com> wrote in message
news:7e******** *************** ***@posting.goo gle.com...

Hello,

Using Access2000, WinNT.

Using the Immediate Window, I can view the results of my VBA code as
it performs operations/calculations on my data. Now that I have all
the bugs worked out, I want that same debug.print information sent to
a form so a user can see what is happening as the data is being
processed. How can I do that?

It's not so much that I want the Immediate Window to pop-up over my
form but rather getting the same data generated using the debug.print
statement into a scrollable text box on a form. This way a user can
see procedure calls, failure/success results, etc.. as they are
executed in the module.

Any ideas are greatly appreciated!
Tony

[Rich P]

You can use the SysCmd function for that.

Sub something()
Dim RetVal As Variant

For j = 0 to 50000
'do somthing
RetVal = SysCmd(acSysCmd SetStatus, j)
Next
End Sub

After the first Paren -- SysCmd( you get a dropdown with something like
15 selections. acSysCmdSetStat us is the 12th selection. it will write
data, numeric, text, date to the statusbar of an Access Application.
This way, you can monitor your procedures.

Rich

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Bas Cost Budde]

Tony wrote:

Hello,

Using Access2000, WinNT.

Using the Immediate Window, I can view the results of my VBA code as
it performs operations/calculations on my data. Now that I have all
the bugs worked out, I want that same debug.print information sent to
a form so a user can see what is happening as the data is being
processed. How can I do that?

It's not so much that I want the Immediate Window to pop-up over my
form but rather getting the same data generated using the debug.print
statement into a scrollable text box on a form. This way a user can
see procedure calls, failure/success results, etc.. as they are
executed in the module.

To do this, I usually wrap the debug.print statement into a routine, and
call the routine from every point in my code I'd like to see or monitor
something.
Now, the routine can use a switch (probably a value in a table) to
decide where the output should go.

You could even store all items that get 'printed' by calling this
routine into a table, and do something with them later on.

If you want to be able to fill a control on a form with the text, you
would have to pass that control to the routine, maybe as Optional so the
routine can use IsMissing(), and write the text to the debug window if
that is the case.

[Tony]

"Wayne Morgan" <co************ *************** @hotmail.com> wrote in message

Yes, for the items you currently have a Debug.Print statement, just set the
value of a textbox instead.

Example from the Immediate window:
Forms!Form22!Te xt0="Hi there"
Forms!Form22!Te xt0=Forms!Form2 2!Text0 & vbCrLf & "Hi there again"

Thanks for the reply Wayne,
I updated my code as suggested. Works great until I added it to a
certain procedure. This particular procedure updates records in an
ODBC connected LotusNotes dbs and therefore takes a while to process
completely through. As a result, the messages stopped appearing in
the form until the procedure was finished. This kind of defeated the
purpose of displaying the messages as they were processed. So, as a
solution, I put a DoEvents after updating the form control and before
a call to refresh the form. Adding the DoEvent solved the problem but
as I read more about DoEvent in this group, I wonder if that was the
best solution?

Anyway, thanks for all your help.
Tony