MS Access 2010 - Constantly bump into Run-Time 3734

wbulckens

New member
Local time
Today, 12:02
Joined
Jan 27, 2015
Messages
5
Hi Folks,

I'm desparately looking for a solution for this very annoying problem ...
I've added a zip file with a stripped down version of my application. It enables you to reproduce my problem.

In short:
I have 3 accdb files: one "classic" frontend and backend situation, plus a third file that contains a query that is called from the frontend file.

The problem is that when I run my (very simple) code that calls the query in the third accdb, I keep running into RT error 3734.

I've been looking for a solution for 2 days already, I've searched all kinds of websites but no luck so far ...

Please help me, this has been driving me mad!

Thanks
Wim
 

Attachments

I, like many on this forum don't download example db's without having some idea of the provenance - and with respect especially from a first post.

So you have better explain - what is runtime error 3734?

What is the code you are using?

And what part of the code generates the error?
 
FYI, moved thread from introductions forum.
 
Hi guys,

Thanks for your replies.

In the zip file there is only one sub ...
And it's not very big (+/- 20 lines of code)

The code copies the results of a query (in the 3rd accdb) to a local TMP table.
The code works perfectly, but when you switch between the form's Design View and Normal View, you get the 3734 run-time error, which means that the database was put in a state where it can't be changed (exclusive). And that's silly, because I'm running it locally on my machine.

I hope someone here knows a way to get around the issue.
It shouldn't be rocket science, but I'm already working on it for more than 2 days.

Any help would be very much appreciated!
Wim
 
To JHB:

Thanks for your suggestions!
It seems to work for this form.

There was also another form in my application with a similar behaviour.
I will test your suggestions on that form as well, and if that also works, I will be extremely happy!

So many thanks already JHB!
I will let you know the outcome.

Wim
 
Hi JHB,

It looks like your DBENGINE instead of my WORKSPACES did the trick!

I'm very grateful for your help
Wim
 
..
It looks like your DBENGINE instead of my WORKSPACES did the trick!

I'm very grateful for your help
Wim
Yeah - and then don't "open" the current database twice, but use CurrentDb to get a pointer to it! :D
 

Users who are viewing this thread

Back
Top Bottom