Search results

You are the second person to answer my post that did not actually read my post. I spent time writing it carefully to explain the process that I've already been through. As I stated in the post, I removed the attachments and the attachment field in the one table that held them. And, yes, the...

That is a good next step.

I see; you are correct. That is a different approach. I did not mention in the post that, in a different attempt, I had also created a new database and used the Import option to import in all the objects from the old database. That was actually the first thing that I did, and that did not fix...

Really? Did you even read my post? And did you read any of the stuff from the links you sent me? They do not apply.

Yes, in my post, I believe I described already doing just that.

I am attempting to compact and repair a local Microsoft Access 2016 database that is being used as a back-end. Nine out of 10 times, the compact and repair process gives this message: The Microsoft Access database engine could not find the object ‘MSysComplexColumns’. I am not certain, but I...

Here is the logic that I would use behind the command button: Step 1 Get a list of values already used in the Moderator Decision field of the records in the subform. I'd suggest using a recordsetclone and looping through the clone records to build a comma separated list. For example, if the...

Also, because we are using late binding, I changed wb1 to Object rather than Excel.Workbook.

I got the same results that you did, but I fixed the problems. You had sort of a mixed bag. (1) You were declaring your Excel app variable using late binding, yet you had maintained the reference to the Excel object library in your References. I fixed this by removing the Reference and by...

You might try CreateObject() or GetObject() to obtain your Excel application object rather than New Excel.Application I have used both of those alternatives in the past.

If I am remembering correctly, an Excel application object that is private to a procedure will automatically close when code gets to the end of the procedure. In other words, if you want to keep the Excel app open after a form is closed, the Excel app variable has to be defined in a public...

Here are the references: Visual Basic for Applications Microsoft Access 15.0 Object Library OLE Automation Microsoft Office 15.0 Access database engine Object Library Microsoft Excel 15.0 Object Library

It did NOT create a new instance of Excel. It stayed within the one that was originally opened.

crowegreg, I tried out a nearly identical set of code (I used Sheet3 instead of Sheet1) and ended up with a pivottable on Sheet 3 and a new chart started on Sheet1. I was using Access 2013 and Excel 2013. Here's what I used: Public Function TestExcelPivot() On Error GoTo Err_Handler...

I have been working with Microsoft Access and VBA for over 20 years. I currently provide live help, development, and long-term support at extramiledata.com. There are some useful Microsoft Access and VBA examples on the Code Snippets and Tips page of the web site. Carl Connett Owner, Extra...