After splitting database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm a newbie......so thanks for bearing with me!

After I split a database I'm unclear as to which file I should use to make
design updates, front or back end?

Thanks,

Christine
 
Christine said:
I'm a newbie......so thanks for bearing with me!

After I split a database I'm unclear as to which file I should use to make
design updates, front or back end?
Click to expand...


If you want to change the design of a table, you'd do so in the backend.
Any design changes to other objects would be done in the frontend.

Remember to compact the backend after design changes, and refresh the links
in the frontend.
 
depends on what design changes you're making.
normally a BE db holds only tables, and a FE db holds all other objects (and
occasionally one or more tables with data that changes never or rarely, or
data that is specific to the current user). so if you're changing a table
that resides in the BE, you must make the changes in the BE (hopefully this
would be a rare occurrence in a db that is in use).

if your database is used by more than one user, you should have a "master"
FE db. design changes to objects in the FE should be done in the master
(*after* you've backed it up!), and then the "new" master FE db should be
copied to all appropriate workstations - overwriting the previous FE db on
each PC.

hth
 
Hi Tina and Joan,

Thanks for your replies. Unfortunately, I'm still confused...not hard to do!

I come from a Notes background (which I understand is a whole different
beast) and in "Notesland" I would make the Db a template and make all changes
to that template and simply refresh the design which would replicate out to
all instances of the Db.

In this Db there will only be one copy of the Db but needs to be shared by 4
people within the group. Since I'm still confused as to how to keep the Db's
insynch, is there any benefit to me splitting the Db at all? If not, can you
tell me how I go about putting it back together?

Thanks,

Christine
 
In this Db there will only be one copy of the Db but needs to be shared by
4
people within the group. Since I'm still confused as to how to keep the Db's
insynch, is there any benefit to me splitting the Db at all?
Click to expand...

definitely yes. it is standard procedure to split a database into BE and FE
files in a multi-user environment. allowing multiple users to open a single
(un-split) mdb file at the same time is an invitation for data and/or
structural corruption.

once you split the database, you have two database files - the FE mdb and
the BE mdb. when more than one person may use the database, the BE mdb
should reside on a common server in a folder that all db users have full
rights to. the tables in the BE mdb should be linked to the FE mdb, and then
a *copy* of the FE mdb should be placed on each user's PC. a user never
opens the BE mdb directly; he/she accesses the common table data through the
FE mdb that sits on his/her PC.

the "master" FE mdb may be placed on the server, but it should *not* be used
for production purposes, or even opened by any user. as the db developer,
you will make design changes to the master FE mdb as necessary (after
backing it up!), and then place copies on the users' PCs, as i said before.

hth
 
Thanks. Am I understanding you correctly that everyone who uses the Db has to
have their own copy of the FE? Let's say that I have a Db that 100 people
will be using, I would have to mail it out and have each of them load the FE
onto their personal drives?

If so, I'll have to rethink using Access for this. It may very well turn out
that 50+ people could use it in the future. I'm afraid it would be a
logistical nightmare to ensure everyone has the correct version.

For now, will it cause any problems to delete one (FE or BE?) of the
versions and keep it as it was before splitting then only I will be able to
use it? If not, can I simply do an unsplit? I can always run reports for
people when needed.

I'm appreciate your input and am sure someone who understood Access better
would be able to follow this but it's too confusing to me :-)
 
comments inline.

Christine said:
Thanks. Am I understanding you correctly that everyone who uses the Db has to
have their own copy of the FE? Let's say that I have a Db that 100 people
will be using, I would have to mail it out and have each of them load the FE
onto their personal drives?
Click to expand...

essentially, yes. if the users are all on a common LAN, there are various
ways to handle distribution of a modified FE db (email is only one of
several) - but if you're not familiar with Access you may not want to go
that route.

if the users are on a WAN, or some other type of network with slow
connections, then you probably don't want them to "access" an Access
database, period - it usually doesn't work well on such.
For now, will it cause any problems to delete one (FE or BE?) of the
versions and keep it as it was before splitting then only I will be able to
use it? If not, can I simply do an unsplit?
Click to expand...

you can just delete either the FE mdb or the BE mdb - each file has vital
components of your database. to "unsplit" the database: simply back up the
FE mdb (just in case); then open the FE mdb, delete the *linked* tables, and
import the tables from the BE mdb. do a compact/repair. then test the
database by opening forms, reports, etc to make sure they work the same as
they did before you "re-unified" the database.
I'm appreciate your input and am sure someone who understood Access better
would be able to follow this but it's too confusing to me :-)
Click to expand...

Access is a very powerful tool, but it does take a substantial investment of
time/energy/patience to learn to leverage that power effectively - much more
so than the other Office Professional software programs. if you ever decide
to delve more deeply into it, here is a link you will find extremely
useful - and the newsgroups are always here to help with specific
problems/questions, of course. good luck!
http://home.bendbroadband.com/conradsystems/accessjunkie.html

hth
 
Christine said:
Thanks. Am I understanding you correctly that everyone who uses the Db has to
have their own copy of the FE? Let's say that I have a Db that 100 people
will be using, I would have to mail it out and have each of them load the FE
onto their personal drives?

If so, I'll have to rethink using Access for this. It may very well turn out
that 50+ people could use it in the future. I'm afraid it would be a
logistical nightmare to ensure everyone has the correct version.

For now, will it cause any problems to delete one (FE or BE?) of the
versions and keep it as it was before splitting then only I will be able to
use it? If not, can I simply do an unsplit? I can always run reports for
people when needed.

I'm appreciate your input and am sure someone who understood Access better
would be able to follow this but it's too confusing to me :-)
Click to expand...

Just a suggestion...
You began by asking about updating a split database, Joan provided an
appropriate answer for that. Then you suggested that you would need 4
people to share the "database". You later modified that, saying that you
might have 100 (then later 50+). You've got people here guessing what you
are in need of. It's apparent that you are struggling with the concept of
and reason for a split database. You might want to consider posting what it
is you are attempting to accomplish in more general terms, then let some of
the people here fill in the blanks for you.
 
OOPS!
you can just delete either the FE mdb or the BE mdb - each file has vital
components of your database.
Click to expand...

that should read

you CANNOT just delete either the FE mdb or the BE mdb...

sorry!!
 
Thanks Randy. You're right. I was jumping around and apologize.

Currently the Db will only have 4 people who would like to access it
however, when I got the responses as to how to handle it it made me think
ahead and the group is 50+ people who at some point may have to use it.

When I used the 100 people example, it was just as a for instance, just to
help me understand it.

I think I'll have to just go back to using something I'm more familiar with.

Thanks for all the input.
 
Back
Top