Last issue.. Hopefully.. Date Stamping

[stupesek]

Ah found it.. hear is the report.

[stupesek]

Yes I used to print one [ReportNumber] at a time. Behind a button that looked at [DateReported] if it was null it would stamp that field with Date() then print that record. If it was not null, the record already had the proper print date in [DateReported] and would print the record without changing [DateReported]. One [ReportNumber] at a time. Again cumbersome if I have a lot of reports and especially with the need to email PDFs these days. And though in database speak, what I am printing is ONE report, it is actually a stack of many smaller reports. You can hopefully see that by the attachment on earlier post.

[weekend00]

So you actuall want them in seperate PDFs, right?
Does it matter if you release many print jobs?
----I still did not get what is the hard part for you.

[stupesek]

I need the flexibility to print the report as one copy PDF or paper or 3 part carbonless is how the report goes to my customer in hard copy form. When paper printing I will have several customers reports printed at one time.

I apologize for not getting my thoughts across clearer.

[weekend00]

What a fool I am!
Maybe I just can not link things in computer with actual work.
Or I am just have nothing to do and come here to grab you to talk with me and waste you time.

I still don't understand what you need.

Let the real wiseman to help you out: RuralGuy, NTC, ajetrumpet...
please send private message to them and get help.

[stupesek]

I am leaning this direction at the moment, does this make sense?

-I have a date stamp update-query that works just fine. (Stamps the date if [DateReported] is null, returns nothing if not null)
-I have a report based on another query that works just fine.
They will use the same "Begining Report Number to print:" and same "Ending Report number to print:"

Can I put the two queries together in code and not have the automatic pop-ups that come with update queries?

[weekend00]

Ok, by my understanding, you want to work this way:

in your form, you have a button and 2 text box for "Begining Report Number to print:" and same "Ending Report number to print:" (if you use popup, you can save the input in variables.)

when the button clicked:
check [DateReported] for every report number and update if needed;
print the report using "Begining Report Number to print:" and "Ending Report number to print:";
print another report using "Begining Report Number to print:" and "Ending Report number to print:";


What else do you need to do?
Which part do you have difficulty?

[stupesek]

Let me see...

1 Click a button

2 Pop up form opens - Asks for "Beginning" and "Ending" [ReportNumbers] to print.

3 UpdateQuery runs that uses those numbers to return: Is [DateReported] null then [DateReported] = Date() else "do nothing". 'This stamps the field I want date stamped at the time of first printing.
--Also, I *do not* wish the accompanying pop-up boxes that warn the input person; "You are about to do ****" and "You are about to modify 'n' records. Are you sure?" I want to suppress them; and I want the resulting table suppressed. User does not need to see these at all.

4 Report is generated using the same criteria as in step two to generate "multiple"
reports or a batch of reports (different customers and different report numbers though all numerically in order)

5 Print preview

6 User Prints the reports (1-3 copies depending on the need at the time and multiple copies not collated because it will be 3 part carbonless paper)

7 User closes the report.

Those are all the logical steps I can think of at the moment.

I was originally thinking I could run a report that would "Date Stamp" a field in a "table" at the same time the report was generated.

[stupesek]

As a side note.. I am a small Agricultural lab that caters to farmers and their needs, so I have to use the term "field" in two totally different ways.

[weekend00]

you can suppress the message "You are about to do ****" and "You are about to modify 'n' records. Are you sure?" by using:
currentdb.execute "update....."
instead of
docmd.runsql "update...."