Search results

Ran downstairs and outputted a report to Excel on my coworker's computer (running Office 2013 and Access 2007) and it worked fine. So, it is either something with my Office 2010 software or perhaps the operating system (hers is Windows 8, mine is Windows 7). Not sure. Either way I am not...

So, I read through Allen Browne's informative page more carefully and discovered the Service Pack 2 update he is referring to is indeed the Office 2007 one. Well, that was already installed long ago. I also noticed that my error messages are not the same. If it were related the the Office 2007...

I may also need this one for 2007 :confused: http://www.microsoft.com/en-us/download/details.aspx?id=5 Will see tomorrow and let you know :)

Ok, so I found this SP2 update for Office 2010 (the rest of my office software is 2010): http://www.microsoft.com/en-us/download/details.aspx?id=39667 Hopefully this will fix the problem. I have high hopes because my coworker's computer has Office 2013 so maybe that's why it worked from her...

Thank you for finding this info. It's strange that it was working fine on my computer up until now but the Service Pack issue seems like a likely culprit. To be honest, the last time I outputted a report to Excel it was on a coworker's computer (different OS); however I have done it from mine...

I made it myself in Access 2007 start to finish including all the code. Here is the exact error message when I alter the code according to your suggestions (incidentally, the same error as before with my code). All I can say is that with or without code the function of exporting a report to...

Used simplest possible code: Private Sub btnExcel_Click() DoCmd.OutputTo acOutputReport, , acFormatXLS End Sub If I change acFormatXLS to "acFormatTXT", it works fine. Once back to XLS or XLSX I get output errors. I am about ready to give up for the moment. It seems very odd that this...

Yes 2007. I know, I thought it was strange too but I checked and rechecked because I had the same idea. I tried using code and get a different error. When I try putting in the newer Excel format (acFormatXLSX) I get a message that says "the format in which you are attempting to output the...

In a macro you can only export to the old versions (I am using Access 2007). I will try using code instead and post back. It is worth a shot.

Sorry, some of them have a button with a simple macro (see pic) The rest I am just going up to the Ribbon and selecting External Data > Export>Excel. NONE of the reports are exporting to Excel. It doesn't matter whether they have a button or not. Some of them have no code at all anywhere in...

By the way, PDF works fine. This is just an Excel issue.

All of the sudden, when I go to export my reports to Excel I get an output error (see pic). I have done this exact same thing dozens of times in the past without issue. I tried repairing Access but it did not work. There is no code being used to output the reports. Has anyone ever seen...

Thank you for all your replies. We need to use both units of measurement interchangeably and at a moment's notice. So, even if a project was executed in the US using feet as a unit of measurement, if we are going after a project in Japan, we will put the meters down in our proposals...

ha ha, I just read in my OP that it started happening when updated to Windows 7... So it must have magically repaired itself. Maybe an Access update??

Now that my computer has been upgraded from XP to Windows 7 this is no longer a problem.

We all know the rule that calculated fields should not be stored in tables but is it ever ok to tweak this rule? Please hear me out... My database is for an international architectural firm. The US projects use the imperial system (feet) but every other country uses the metric system. These...

You would have to put a field in your table and use code to assign the bound control a value. As namliam has stated, this is not advisable. A better idea would be to put your if statement into a query like this: ExprName: IIf([Invoicepaid]=True,[ServPrice],0) Then you can use that query...

MarkK: This is great. Exactly what i was looking for. Thank you!

Good:) I had that problem with one of my concatenated fields too and it helped to make a query on a query. So I made a query just to concatenate and then used that query in the form/report's recordsource (another query) instead of trying to use the concatenate function directly. Not sure why...

@Leo_Polla_Psemata: Did you get manage to get this working?