Search results

Open a recordset based on the table and run a loop to send the reports. There are several ways to send emails via VBA. Search the forum for email and you will find plenty.

As far as distributing your application, there are some conciderations you need to make. Keep in mind, If you distribute an mdb, your clients will have access to the source code. If you distribute an mde, with a front end and backend, you will have to create a linking tables utility. Also...

Copy and paste - format to look like you want. Then add your fields and it should be that easy. If you really wanted to (or if the documents are constantly changing) you could add the document data into a table for easy edits.

Oops, Docmd.SendObject

I would suggest skipping the mail-merge entirely. Create a report that looks like your doc, and use the docmd.sendto (if you're using outlook) command to send the email. I generally try to stay away from using external items (docs, xls) if I can help it.

If there are no major differences in the PC, then I would uninstall and reinstall access. If this isn't an option, or too time consuming, you could write your own left function. Call it LeftNew or something. But that is an access error, probably in your VBA reference. Also, check for any...

I'd be interested in any leads. I don't know if I would be willing to pay for "Maybe" leads. What I mean is that if there was a definite project I would be willing to pay a percentage of the final price as a "finders Fee".

Are you storing the user's picture (or path) in a table? Maybe you could setup your table with the picture path, and user. For the default, make the user = 'default' and the path be the path to the default picture. Each user will have an entry in the table under their user name. On the open...

Hardcoding the path should work fine. I've also experienced that if you just save it with the correct picture, that it will stay that way. I'm guessing that the code you submitted runs on the open event?

Yeah, yeah, yeah. My apologies to both you. benheaven1, if you have changed a line of code in here (most likely the name of the import spec) you will get this error. You can create a new spec with the correct fields and it should work. This works fine, but is ugly to maintain. As far as...

I don't know much about the email servers, but I would imagine that there is the some sort of log produced. If not, there is probably an option to turn on logging. When the log file is produced, you could easily import it into an Access database.

This would be better suited in a module. This way you could add an error handler to send an email incase of a program error and also send an email incase certain criteria are met.

You can nest withs, however only the most current with is referenced when the code incounters a '.' (dot). Such as: With rstRecordset Do until .EOF 'references the recordset object with objExcel .Range("A1").select 'references the excel object .MoveNext...

What line is it failing on? Step through the code to find it.

Replace your line: Set AttachME = Maildb.CreateRichTextItem("C:\stock_tracker.xls") With: 'create the file item Set AttachME = Maildb.CreateRichTextItem("File") The next line in your code fills the item with the file: 'fill the file item with the file Set EmbedObj =...

It's pretty close, but not quite the same. I believe that you need to change your line "Set AttachME = Maildb.CreateRichTextItem("C:\stock_tracker.xls")". Replace the "C:\..." with "File". In Lotus you need to create the text item of a "file" and then fill the item with the file (name and...

I probably send out 2-3 thousand emails a day with attachments from Lotus Notes. Here is the code I use. Set objRichTextAttach = objDoc.CREATERICHTEXTITEM("File") Set objAttachment = objRichTextAttach.EMBEDOBJECT(1454, "", strFile)

Do you have a table of filenames for the images? If so, are they related by membership number? It would be easiest to link them and then create a report / query and just sort it. If not, then you have to do alot of parsing the information to retrieve the records first associated by membership...

You cannot make the database not open, but you can make it close right after it does. The easiest way is probably to use a recordset that queries the local table and the linked (to backend) table to return the versions. Keep in mind that these versions are manual updates to tables on your...

If you are using a front end on the user's pc, and a back end on a server (for all users to access) then you shouldn't have a problem with pc changes. Just make sure that the user always has the most recent version. In a client - server environment this shouldn't be an issue. If you really...