question creating multiple front-ends

Aha! The virtues of being selectively industrious
Thanks much!

-Amit
-----Original Message-----
This is what you need:

http://www.granite.ab.ca/access/autofe.htm


"Amit" wrote in
message
...
One follow-up thought.

If I install front-ends on each desktop (as opposed to
on
the shared drive), this will entail going to each
desktop
and updating all front-end every time a change is made.
I
guess more physical activity is good for whoever will do
the maintenance

-Amit

-----Original Message-----
Oops, didn't see other reply.

At least we concurred!

TC


"TC" wrote in message
...

"Amit" wrote in
message
...
MS Access 2K, Windows XP
========================
I have a database which is to be used by
multiple "groups"
of users, and each group may have different reports
and
some variation in forms. So, I'd like to split the
database into a BE and FE, with different copies of
FEs,
one for each group, linked to the same BE.


================================================== ========

Splitting the db is a good idea for other reasons
also.
For example, if
the
db is not split, it is difficult to roll-out new
code
versions without
overwriting the user's data. With a split structure,
you just copy a new
FE
over the old FE(s), and the users' data remains
unchanged in the BE.

But, aren't you heading for a maintenance headache if
you have two
different FEs? What about the programs that must be
common (unchanged)
to
each FE? You run the risk of accidentally having
different versions of
those
programs. personally, I would try to incorporate
all
the necessary
functionality into one FE. For example, when you
called a report from a
main menu, the main menu code could pick from several
different versions
of
that report, depending on the logged-on user's name,.
group membership, or
whatever.


I have two questions.

First question is: how do I create multiple copies
of
FEs
after splitting the database?

a. copy-and-paste the FE created after the split,
or
b. create a new empty database (FE) and then import
tables
from the existing FE, and link it to the BE, or
c. any other?

Are both a. & b. OK? Or, is one preferred over the
other?
Any advantage of one over the other?

a. is fine AFAIK. Of course, after making changes in
a
FE, you would
always
compact it and do a "compile all".



================================================== ========

Second question is: Should the FEs be placed on the
individual desktop of all the users, or on the
shared
drive? The BE is on the shared drive.

Put the FE(s) on each individual desktop. Or, if you
put it/them on the
server, there must be a seperate copy for easch
user,
strange as that
may
seem. IOW, multiple users must not share the same
copy of an FE.

HTH,
TC


Thanks for any help. This is the first time I'm
creating a
multi-user, multi-FE database.

-Amit




.



.

I put a small VB program (actually in Access) that each user runs each day before they use the main database. This program copies a fresh copy of the front-end from the server to their computer each day. That way if I make an update to the program each user will get the update. It always eliminates the need to compact the front end since they are getting a new, compacted database each day.

"TC" wrote in :


Giving "high up management" ANY view of the data is a seriously
misconceived idea IMO!



VBG

Tim F