Re: Mailing List code bug for FredG
From: fredg (fgutkind_at_example.invalid)
Date: 03/19/04
- Next message: Dale: "Subreports that disappear when db is split"
- Previous message: fredg: "Re: parameter box"
- In reply to: Jeff Conrad: "Mailing List code bug for FredG"
- Next in thread: Jeff Conrad: "Re: Mailing List code bug for FredG"
- Reply: Jeff Conrad: "Re: Mailing List code bug for FredG"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 23:33:00 GMT
On Fri, 19 Mar 2004 12:18:55 -0800, Jeff Conrad wrote:
> Hi,
>
> This message is mostly for Fred, but anyone else is most welcome to join in.
>
*** snipped ***
> Here are the steps to reproduce:
>
*** snipped ***
>
> 2. OK, in my test data I have 16 vendors, but I don't think it matters how
> many. I have 30 labels on a ***, but again I don't think this is
> significant either. For the sake of testing please try and match these
> requirements.
>
> 3. Open the report from the database window and select any number for
> starting position and only 1 repeat. Should be one page no problems. Close
> the report.
>
> 4. The MAGIC number for me is ANYTHING after 3 pages in length for the
> report. So, for example, if I say 0 starting and 4 repeats then the
> "weirdness" happens!!! OK, Jeff what "weirdness"!!
>
> You must do this EXACTLY like I say!!
> First Test:
> - Open the report and select 0 and then 4
> - At the bottom left corner are the page selectors
> - BEFORE DOING ANYTHING ELSE click the far right one that should take you to
> the last page
> - You should see a slight screen flicker, but the page does NOT change.
> You're still on page 1!
> - Think that's weird? Now try clicking the button that will advance the page
> one at a time. The number will change to 2 and the new labels will also
> appear. Fine. Now keep GOING one page at a time and see what happens!!!! The
> labels displayed do NOT change AND the number will just keep going and going
> and going to infinity!!! Even if I change the view to show six pages at a
> time it will show six pages of the same thing over and over and over even
> though I know it is only a three page report!!! Weird! If I hit the last
> page button it just goes bonkers.
>
> Second Test:
> - Open the report and select 0 and then 4 again
> - Advance the report by one page at a time WITHOUT hitting the last page
> button. The numbers correctly stop at 3 and the labels displayed are fine.
> So what's the problem with the last page button and this code?
>
> 5. I was VERY afraid to actually hit the print button for fear of an endless
> stream of pages coming out! But, to complete the test I bit the bullet and
> hit print. It correctly printed only 3 pages even though my screen said 99
> pages at that moment! Whew!
>
> 6. One last note before everyone goes "I'm not seeing this." This
> "weirdness" only happens on Access 97 and 2000. I do NOT see this behavior
> on Access 2002 or 2003. I have done a LOT of testing on various operating
> systems and page numbers, but it only occurs on 97 and 2000. For the last
> two versions no matter how big the report was (and I tried really big)
> clicking the last page button correctly took me to the last page after a few
> seconds. And yes, I believe each system had the latest service packs and Jet
> updates.
>
> So my questions:
> 1. Can anyone else see this on 97 or 2000?
> 2. Why does this problem happen on 97 and 2000?
> 3. Anyway around this? The users want to know how many pages are going to
> print, but they're afraid to hit the print button!
>
> Thanks for any comments and/or thoughts.
> Jeff Conrad
> Bend, Oregon
Jeff,
1) I don't have the form with the layout you are using, so of course I
can't comment on that. I use a couple of controls on a form and simply
enter the number of labels to skip and/or repeat.
2) The code you are using uses nextrecord, printsection and movelayout
in the Print Event to advance (or not advance) as needed. If you don't
actually print (or preview) the pages, one at a time in order, the
events do not fire and Access 'gets lost'. When you went to the last
page first that's what happened.
It's a non-issue for me, as the idea of generating labels is to print
them, otherwise filter out the ones you don't want in the report's
record source. As you said this has worked properly all along ....
(until you got to experimenting) <g>.
In the Marx brothers movie "Coconuts" (I think, or maybe "A Day at the
Races") when Margaret Dumont complains "Dr. Quackenbush, when I go
like this 'cough', 'cough', it hurts", Groucho Marks replies 'Don't go
like this."
If this remains an issue, I would suggest you use an alternative
method to print multiple labels, using a table with as many records as
you might eventually want to print.
Allen Browne has information at his web site
http://members.iinet.net.au/~allenbrowne/ser-39.html
-- Fred Please only reply to this newsgroup. I do not reply to personal email.
- Next message: Dale: "Subreports that disappear when db is split"
- Previous message: fredg: "Re: parameter box"
- In reply to: Jeff Conrad: "Mailing List code bug for FredG"
- Next in thread: Jeff Conrad: "Re: Mailing List code bug for FredG"
- Reply: Jeff Conrad: "Re: Mailing List code bug for FredG"
- Messages sorted by: [ date ] [ thread ]