does it give you an error message when you try to email? or does it just do nothing?

No error message. Just nothing. It shows it is exporting but it does not get sent as evident in my Outlook Sent folder. We also did some tests to have an invoice go to our own emails in the office and nothing..

check to see what report other users have in their printer setup under email in the invoice area at the bottom, maybe its just a bad file path

Is the invoice a customized one and did it ever work before?

Yes it is custom and in fact I was going to report on this forum that I changed the location of my customized report from my C drive. The path for my custom invoice for the Printer properties is correct. So I decided, to copy the actual customized invoice to the data file on the server. I kept a back up copy. I then changed the path to my Reports Folder on the BVData directory. I then tested one and it worked to my email. I am going to actually try another one to an actual customer's email address and see if it actually works. So far though it is encouraging. My email worked before with a customized invoice and I always kept it on my C drive separate from the DATA directory on the server. I will report back once I have tried another and let you and others know as it may help others.

What I just said was incorrect. I copied my customized invoice to my Reports folder on my Business Vision program file directory on my C drive. I did not put it in the DATA directory on the server. I just tried this on another workstation and it didn't work.

We have our custom invoice saved to the data folder on the server so that when we update it converts with the data if necessary.
So did it get converted to a newer version when you updated or not?

Hi GUSB. I always read to make sure you have a backup copy of your customized report (invoice) before updating. This is because if you update and the file is converted it will overwrite the .rpt file. So, I have always kept it separate from my data and also separate from my Reports Folder on the Program Files directory, so as not to overwrite the customization of the Invoice -plain paper.rpt. So, now that you say this, the custom report is probably not converted since my last update. I am using BV STandard Edition 2015 v7.75. But having said this, none of my reports are on the Data drive/directory. In fact, none of the program files are on the server. The program files are kept on each workstation. I have a LanPack 5 user. So we are all using the same customized report. Also, don't updates and patches just affect the program files and not the data? My data directory is separate from my program files. When I update, it updates the program files. I don't update anything on the server except for Pervasive, if necessary

Hi GUSB. I always read to make sure you have a backup copy of your customized report (invoice) before updating. This is because if you update and the file is converted it will overwrite the .rpt file. So, I have always kept it separate from my data and also separate from my Reports Folder on the Program Files directory, so as not to overwrite the customization of the Invoice -plain paper.rpt. So, now that you say this, the custom report is probably not converted since my last update. I am using BV STandard Edition 2015 v7.75. But having said this, none of my reports are on the Data drive/directory. In fact, none of the program files are on the server. The program files are kept on each workstation. I have a LanPack 5 user. So we are all using the same customized report. Also, don't updates and patches just affect the program files and not the data? My data directory is separate from my program files. When I update, it updates the program files. I don't update anything on the server except for Pervasive, if necessary

We keep a copy of the custom reports in a separate location just for added security, any custom reports we use are in with our data and all the users can be set to link with it. You need only to copy and paste it into your data. If you haven't already rename any custom report so there is less confusion if something happens but remember to point each user to them after. This way you don't have to copy them to each workstation. When you update a workstation and start to use the data base it will get converted automatically along with the rest of the data to my understanding, rather than thinking you need to update the server to achieve it.