Question Printing problem

[Joe8915]

DB split
2007
Having issues, some users can print the selected object and some can't some of time. This has me real scratching my head. I can't get it where it happens all the time. Some times it works and some times it don't. It will print a some other form. On time it printed a hidden form. It not happing to all the users, just a select few. All using the same printer, all have the same permissions. I have deleted and added new print buttons. All are using the same operating system.

Any thoughts?

 

[Trevor G]

Have you thought of creating a report that is a replica of the form and use a macro to print preview based on the selected record, that should clear your issue.

If not perhaps upload a sample and someone will take a look

 

[dfenton]

Reports are for printing.

Forms are for editing/viewing.

Forms should not be used for printing.

 

[ghudson]

Reports are for printing.

Forms are for editing/viewing.

Forms should not be used for printing.

I agree but sometimes it is easier to print the current record in a form (for auditing purposes) than having to recreate a report of the same information and it would be a lot of unnecessary work to get a report to look like a form.

This is what I use to print the current record in the opened form....

    Printer.TopMargin = 0.25
    Printer.BottomMargin = 0.25
    Printer.RightMargin = 0.25
    Printer.LeftMargin = 0.5
    DoCmd.RunCommand acCmdSelectRecord
    Me.Printer.Orientation = acPRORLandscape
    'DoCmd.PrintOut , 1, 1, acHigh, 1, False
    DoCmd.PrintOut acSelection

 

[dfenton]

Easier for whom? Maybe easier for the developer, but as you're finding out, it's obviously not easier for the users.

Forms are for editing/viewing data.

Reports are for printing.

If you maintain that distinction strictly, then you'll enounter fewer problems.

But, it's true, it WILL be more work for the developer, but isn't it the developer's job to put in the work so that the users don't have to?