Print statement in a procedure or form appears to act as a stop


#1

Can somebody please try this:

openprocedure "insert a procedure name here"
print ""
message info("dialogtrigger")

I cannot get any statement to execute after the print statement within a procedure. Similarly, if I try to print a form. No problem if I try to print the data sheet of the active database or another database.

This problem exhibits on three differently configured computers.


#2

I am finding the same thing. I group up, open a form, print, and then it should remove the summaries and close the form, but it stops at Print.

It is not a problem with printtopdf, but that requires a lot more work to get the options I want.


#3

I can confirm it. I tried this one:

openprocedure ".AreaCoder"
print ""
openform "MapLetter"
message "I've just printed that procedure and opened the form."

After printing nothing happened. [Well, to be very accurate, the first time line 3 wasn’t there and I got an alert saying something like Dialog aborted, after which nothing happened. The second time I ran that one some sort of message box appeared for about a tenth of a second which I couldn’t read. Then I added line 3 and after printing finished, nothing.
I put the line

Pause""

after print and I then consistently got a flashing alert, but it didn’t open that form.

So there does seem to be some problem here.

(Once again replying from my mail program didn’t post here.)


#4

I’m so pleased that this is a genuine bug and not just an aberration on this side of the Date Line.

I’ve seen this all the time - I set up an extremely long message and it was easier to see that it was, in fact, that message which flashed on and off. My recollection is that it doesn’t appear if I hit the Cancel button.


#5

I can confirm it. I tried this one:

openprocedure “.AreaCoder”
print “”
openform “MapLetter”
message “I’ve just printed that procedure and opened the form.”

After printing nothing happened. [Well, to be very accurate, the first time line 3 wasn’t there and I got an alert saying something like Dialog aborted, after which nothing happened. The second time I ran that one some sort of message box appeared for about a tenth of a second which I couldn’t read. Then I added line 3 and after printing finished, nothing.
I put the line

Pause""

after print and I then consistently got a flashing alert, but it didn’t open that form.

So there does seem to be some problem here.

Michael Kellock

28 June2018 at 8:43 PM

michael

    June 29

Can somebody please try this:

openprocedure "insert a procedure name here" print "" message info("dialogtrigger")

I cannot get any statement to execute after the print statement within a procedure. Similarly, if I try to print a form. No problem if I try to print the data sheet of the active database or another database.

This problem exhibits on three differently configured computers.


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

logo

** William Conable***, Alexander Workshops, LLC*

Mobile: 509-270-7492
815 Villard St.
Cheney, WA 99004

www.alexanderworkshops.com

Designed with WiseStamp - Get yours


A procedure printing app