Search results

You can't look up multiple fields with one DLookup like that. You would need one for each field. LastName would get its own. Title would get its own, FirstName would get its own and then you would concatenate those three DLookups together.

You can try exporting that report into another database, delete the existing one and then import it back.

Go to the VBA Window and to DEBUG > PROJECT and see what happens. Does it say there's a compile error and then go to it? Do you maybe have an Excel Reference set? If so, then remove the two constants (xlCenter and xlBottom) as that could be conflicting. The constants would be there in case...

Post the code again so we can take a look.

The function is called by using SendTQ2Excel "TableOrQueryNameHere" You don't need to set the library because it is already there (it is the Access Database Engine - or ACE as it is known, which is the Access team's version of DAO).

Ah, so me. Okay, have a nice day.

What attitude problems? If there are any of those it would be caused by you not following normal forum ettiquette which is going to be the same no matter which forum you visit. So, if you post multiple times somewhere else too, you are going to get the same or worse. Some admins of the other...

It is still doing that even when you have changed the code and then also I assume you deleted the existing back up file there. If so, you may want to use this method for export instead: http://www.btabdevelopment.com/ts/default.aspx?PageId=48

Need is such a strong word. They don't NEED to do that. That is another way to do it. But it can be done the way I showed too, without creation of a new field. Your path may be simpler though for most people to grasp and it will take care of the Time issue if there is a time associated with...

Wow, sorry to hear and I thought we were working your issue. But just an FYI - most forums will have the same rules and stuff so you'd be running away into the same situation. But if you have your mind made up. I guess that's your choice.

Change to outputFileName = "FileName.xlsx"

Query criteria would be [DateFieldNameHere] Between DateSerial(Year(Date()), 1, 1) And DateSerial(Year(Date()), 12, 31)

Yes, because we close it with xlWB.Close and the True after that says to save it. If you want it to remain open just get rid of that line and then put in objXL.UserControl = True instead. What version of Office do you have? What is the value of outputFileName? It still opens the file. It...

I understand but it goes against forum ettiquette and, potentially a banning offense by the mods if they warn and then it happens again. So, just letting you know that you're likely going to piss some people off if you do that.

Please don't post the same question over and over again. This is like the third thread I've found this on.

That would be CloseButtonState(False)

Yes, the extra End If is not supposed to be there. I did forget to put this in which I usually do until it has been debugged and working correctly. objXL.Visible = True That is necessary to avoid having rogue Excel.exe instances out there. If you use Ctrl+Alt+Delete and go to Task...

You need to create a macro and name it AutoExec (exactly like that). In the Action for the macro use RunCode and in the arguments area use: CloseButtonState False If you open the database holding the shift key, it will bypass that so it won't be disabled but if you open it normally...

Sorry, Yes I missed two parts. See the red: Function ExportMyTable() Dim objXL As Object Dim xlWB As Object Dim strFile As String Dim rst As DAO.Recordset Dim i As Integer strFile = "C:\Temp\MyExport.xls" DoCmd.TransferSpreadsheet acExport, ...

Date1 should be [Date1]:#01/01/1983# with # signs instead of quotes. Also, use the NZ function on LeadTime [SAF]+Nz([LeadTime],0)