Share via

SendObject current record only

Anonymous
2012-10-03T11:49:03+00:00

I've been asked to add an email notification to a shared databse on our network. I do have admin rights, but I'm not the creator of the database. I need to send preferablly "rich text and pdf" form of the current record on a form. I really don't want to create a query or report in this database as it is not my own. Also it does not have a primary key, and the ID field is query generated. I was just wanting to see if anyone had a good solution to either emailing a snapshot of the current form or possibly generating a report that is identical to the current record/form based on code.

Thank you,

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Tom van Stiphout 40,211 Reputation points MVP Volunteer Moderator
2012-10-03T12:02:25+00:00

You can use:

DoCmd.SendObject acSendForm

I'm not a big fan of emailing forms - they tend to have a lot of non-essential stuff on them. I would rather create a report.

No PK? Sounds ominous.

The fact that you did not create this database has little bearing on anything as far as I am concerned. If this is your assignment, you make the best of it. If you see things that should be improved, you can discuss with your manager.

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2012-10-03T12:30:52+00:00

    Tom,

          Thanks for the feedback. I think you're example is the best approach for this situation. This task is just a "band-aid" as my total assignment is to design and implement a new database, but 1st is to make slight changes to the origional, because it's used daily. I personally will be sending via reports within my own DB structure, but time wise and functionality does not fit the need within the current DB. It's kind of one of those situations where you're expected to mkae big changes, but at the same time don't change much because of user comfort.

    Was this answer helpful?

    0 comments No comments