error 3251 "Operation is not supported for this type of object"

[mlrucci]

Good afternoon, I am stuck. I have multiple forms with buttons containing vba to import information from an excel spreadsheet into a table in access. Works great. For some reason, when I move the db over to a new db to keep it "cleaned up", I received the error 3251 "Operation is not supported for this type of object". This occurs after the following:


1. Copy the DB to new DB
2. import information from excel spreadsheet to access table and works.
3. Attempt to import via button/vba from any other form (multiple forms with buttons for different imports) from excel spreadsheet to a different table and I received the error code.

It is acting like once I import data to a table, it corrupts the DB. Unable to find helpful information on the error code. It works great in the original DB. Any suggestions except the obvious of not transferring it to a new DB. Access has a tendency to be a bit quirky and would like to keep it cleaned up.
I have attempted to Compact and Repair without resolution either.

Thanks in advance for the help

[June7]

What do you mean by 'copy' - SaveAs or copy/paste in Windows? You are using Access 64-bit?

[mlrucci]

Sorry, wrong word. I don't copy the db. I am importing it into a new db. I am using 32 bit

[June7]

Why do you feel you need to do import to 'clean it up'?

The error is triggered when and with what object?

[Minty]

If you decompile your existing database it pretty much performs the same as copying it into a new blank one.

Full instructions here: https://www.fmsinc.com/MicrosoftAcce.../Decompile.asp

However you problem is probably caused by a reference missing from the new file.
Goto the VBA editor and click Tools¬References.
Compare what you have and the order they are in between the old and new versions.

Finally, I'm in agreement with June, you should only be creating an new DB as a matter of last resort, not as a regular maintenance task.
That would tend to indicate something is not right in your database if corruption is occurring that often.

[mlrucci]

June and Minty, Thank you for your responses. The decompile didn't correct the problem, and the references are in the same order. At this point, the original program is not having issues. It became a common practice for me to do this over the years as Access was very glitchy, and before I put the program live and split, I would import it into a new db. You are probably right that it is unnecessary. In the end, I am not sure why this is happening. Was just looking for a solution. As you know, programing is like a puzzle, hard to put it down when there is a problem. Thanks again

[Minty]

I think we would need to see the code being used and the point at which it errors?
Without that we will be shooting in the dark.

Maybe you could upload one spreadsheet and the relevant parts of the DB that is failing for us to have a look at?

[Micron]

Perhaps when things are copied over to a new db, no thought is being given to References so one or more are missing?

[mlrucci]

So, I am not sure what is going on, but my original db just crashed and it automatically saved the db to Database1 and deled the original. I thought I would get a shot at trying to see if the system would move the objects to new database as I was concerned that again it is corrupt. This happens sometimes when I attempt to make changes to a form or report in Layout. I opened a new db and imported all the objects. Added the appropriate references, decompiled and did CR. Without making any further adjustments, it is now working great. On another note, I did check the references again because I added 2 of them for the picker in for the appropriate excel spreadsheet import, and it was correct for both the references and the order of the references. Currently not having any problems. Go figure. I would like to thank everyone for their input! It is just bizarre

[Minty]

As a further piece of advice turn off the Name AutoCorrect options, they are known to lead to corruption in certain circumstances.
They are in Options ¬ Current Database in the File Menu.