Shared back end data base

[Marco]

Hi. I have two access aplications. Aplication A and B. The back end data of
aplication A is shared in order Aplication B can read it. Sometimes, when
someone is using aplication A and others are using Aplication B, the
Aplication B returns a error /message saing that back end of aplication A is
being used.

I can I solve this problem?

Regards,
Marco

 

[Douglas J. Steele]

Do all the users involved have at least Change access to the folder where
the back-end of Application A exists? They require Read, Write and eXecute,
and should also have Delete.

 

[Todos Menos [MSFT]]

keep everything in a ADP and you won't have to worry about versioning

 

[Marco]

Hi. Thanks for your reply. Well, I put all users with full control, but only
in my computer it works. If I try in my computers with other access security
password it works, but on other users computers it doesn't work.

It seems theres a issue with windows logon. The other users, they are Users,
i'm the administratror.

But, I can't change users permissions.

Any idea?

Thanks,
Marco

 

[Marco]

First no one should be accessing the back end directly. They all should
have their own front ends. All the front ends do not need to be the same
design.

Everyone needs full access (read write delete etc.) to the directly
where the back end is maintained.

It is possible that someone is opening the back end exclusively. They
may or may not be aware of it.

 

[Marco]

Hi Joseph,

No one access to the back end data directly, only from the front-end. Each
user has their onw Front-end

I put everybody with their onw front-end.

Now, users of both aplications have full control to the folder where the
back-end is saved. but the problem persists.

Please help.
Marco

 

[Todos Menos [MSFT]]

don't listen to these kids

Access MDB is obsolete; it hasn't had a single bug fix in a decade

move to SQL Server, kid-- or be stuck maknig $12/hour for the rest of
your life

 

[Marco]

WHAT?

Arron, why do you keep this rant up. Why do you keep changing your on
line name? Do you really think you are fooling anyone?

Note: don't try to answer those questions for us, try to do so for
yourself.

 

[Todos Menos [MSFT]]

eat a dick

MDB is obsolete; ADP is a much superior platform in every possible
manner

stability, ease of development, ease of administration; reporting?
ETL?

ADP wins them all

WHAT?

Todos previously known as Aaron is our local Troll. He seems to appear
most often when school is out.

Todos Menos [MSFT] wrote:
don't listen to these kids
Access MDB is obsolete; it hasn't had a single bug fix in a decade
Arron, why do you keep this rant up. Why do you keep changing
your on line name? Do you really think you are fooling anyone?
Note: don't try to answer those questions for us, try to do so
for yourself.

 

[Todos Menos [MSFT]]

because i'm right-- that's why I keep this up

ADP is a superior platform.


any way you look at it.

can you even run profiler in an MDB? to see what your database is
DOING?