can't create a report because others are using front end database

T

Tina

I have a split database, a front end and back end, both on the network
because everyone shares the same queries on the front end, but whenever we
create a report, we can't save it or it's running slow because two or more
people are accessing the front-end. What can I do?
 
A

Allen Browne

Tina, the whole idea of splitting the database is that everyone gets their
own separate copy of the front end.

Splitting, and then everying opening the same front end is probably the
worst possible configuration. You get none of the benefits of splitting, and
the penalty of attached tables.
 
K

Klatuu

Each user should have their own copy of the front end on their own computer.
Sharing a front end is never a good idea. The application will run faster in
this configuration and you wont have the conflicts with users trying to use
the same objects.
 
T

Tina

Okay, if everyone has their separate front-ends, then how do you sync the
queries into the real one?
 
A

Allen Browne

Once you have completed a series of changes, debugged, tested, and
documented your changes, you can release a new front end for the other
users.

You can copy it to the user's machines across the network if needed. Or you
can use an approach like the one provided by Access MVP Tony Toews:
http://www.granite.ab.ca/access/autofe.htm
 
K

Klatuu

Every copy is the "real" one. It is up to whomever is responsible for the
database to provide a method to apply updates and changes to the front end.

If you are saying that users are creating their own queries and you want the
user created queries to be available to all users -- another bad idea. There
can be no security or data integrity if users are allowed to create and
execute queries on their own. Users should never see anything other than the
forms and reports you create for them.
 
T

Tina

Okay, this may work, but if the users are making the changes on their own
front ends, how do we sync it up with the one on the network and then release
the new front end?
 
D

David W. Fenton

if the users are making the changes on their own
front ends, how do we sync it up with the one on the network and
then release the new front end?

You don't.

The front end that your developer is responsible for will always
replace anything your users create.

If your users want to maintain their own separate MDB with links to
the back end, they can use that to create their own queries and
reports.

If you want to fold such objects into the main development project,
then your users should export candidate objects to an MDB for your
developer to review for incorporation into the main front end code
base. I have never found that my clients think it's worth the
effort, since they almost always have needs that are beyond their
own capabilities, so I end up doing everything but the most trivial
design work.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top