Also note. If you add a button to your form and call it "Print
Confirmation" your manager should not care if that prints a report or a
form. Let your manager tell you what the end results should be, don't let
him tell you how to get there. That's your job to determine how to make it
work. Just make sure it meets his requirements.
If it were me, I'd build the report and make it pretty and let it do what
you need. I'd also point out that this allows you to STORE YOUR ACTUAL
COURIER COST as apposed to some funny number. What if your markup changes
in a year? You'll never be able to determine what your real cost was in the
past. If it were me, I'd store the cost AND I'd store the markup percent in
a separate field. You can default it to 50%, but I'd store it so it could
be changed when needed.
After I built the report, I'd add the button to the form to save the record
and send the report to the printer. I might even have it automatically send
two copies if that is what you want. This would all be much easier. If you
want to make it really really easy, just add code that automatically dumps
two copies of the report to the printer any time you add a new record
through your form.
In short, use the features as intended. Don't just keep doing things the
way someone (who obviously did not know Access) decided to do them in the
past. Printing a screen works, but would you write a letter in Word and
then screen print it? No!
Good luck,
--
Rick B
"Adam - Regus" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Right now, my manager has us prinout the forms, and give one copy to
> the client, one we keep. I am going to suggest to my manager that we
> prinout a report instead, but their entire system for billing is built
> around printing the forms, so I'm stuck for now. And I don't know that
> much about building databases, so I appreciate all the advice!
>
> So Roach, when I copy and paste the code into the text box for "COURIER
> COST", in the after update, I get the following error:
>
> "The expression After Update you entered as the event property setting
> produced the following error:The object doesn't contain the Automation
> object 'text markup'.
> * The expression may not result in the name of a macro, the name of a
> user defined function, or [Event Procedure]
> *There may have been an error evaluating the function, event, or macro.
>
>
> FYI, I'm running Access 2000, so maybe the older version could be at
> fault too?
>
> thanks again,
>
> Adam
>
|