Emmanuel Katto Dubai : What does error code 3734 mean when copying objects from one database to another? (3 Viewers)

[emmanuelkatto24]

Hi team! I’m Emmanuel Katto from Dubai, United Arab Emirates (UAE) facing an issue with merging changes from a client’s version of an application. I used to be able to copy objects between two versions open side by side, but now I’m getting an error when trying to do this. I’ve tested it on multiple PCs and even tried copying files locally, but the problem persists.

Has anyone encountered this issue before? If so, how did you resolve it? Also, does anyone know of a tool that allows exporting selected objects to another database more efficiently? The built-in export feature in Access is a bit limiting, and I’m looking for a better solution.

Any help or suggestions would be greatly appreciated! Thanks!

Regards
Emmanuel Katto

 

[Gasman]

And 3734 is?

 

[The_Doc_Man]

The error suggests that something is wrong with the destination database. It probably is corrupted. BUT it also could happen on the source database if you are trying to do the operation on a copy of the same source file on those different machines you mentioned.

One of the two files has been software-locked by Access. (Which is what error 3734 says.) For future reference, when asking questions of this type, always include the text of the error with the number. Error 3734 is the wordy message that starts with "Database has been placed in a state that prevents ..." and it tells you the DB cannot be opened or locked.

Try doing a compact & repair (C&R) on a copy of each file. I would do the destination file first.

For the record, you NEVER do a C&R on the original, just in case an error occurs. But you CAN (and, actually, should) just do a Windows Explorer copy and paste of the file in case the C&R fails miserably - which COULD happen if the corruption is bad enough. In cases like this, don't use Access to make a backup since the file integrity is at the moment suspected of being bad. Access would just barf. But even if it doesn't, the backup copy would also be suspected of being corrupt. Using a simple copy/paste operation bypasses any attempt to interact with the contents of the questionable file. If the C&R fails, you still have the copy to try something else.

The question remains, "how did it get this way?" That might be unanswerable, but there might be a Windows error log entry involving Access and one or other other of the files - if you could be sure of which machine first recorded the error.

 

[moke123]

Is the receiving database open? I believe you'll get that message.

I generally import the object as opposed to exporting.

 

[The_Doc_Man]

Moke's comment reminded me that the error can also occur if the destination database has already been opened in EXCLUSIVE mode, which includes opening it with something in design mode.

 

[CJ_London]

When you start editing any object I believe that will automatically change the status to exclusive

To copy/paste both db’s need to be open and not edited

 

[isladogs]

I believe the OP is referring to objects being copied by drag and drop from the navigation pane of one open database to another.
This only works providing there are no open unsaved objects in the source database.

See my YouTube video:

@emmanuelkatto24
You have several user names including this and @emmanuelkatto23 which is against forum rules.
You also keep posting questions but rarely if ever respond to the replies received.
Are we all wasting our time bothering to reply?