FE/BE & MDE


G

Guest

I have a couple of questions regarding FE/BE & MDE files. I'm trying to
understand which route I want to take and which is the most secure.

1. If I split a secure db into a FE/BE will the BE be secure as well and
will anyone be able to open it just by clicking on it or will they need the
workgroup to do so?

2. If I was to convert the FE to an MDE file will I need to convert the BE
to an MDE file as well?

3. Do I use my original mdb file to make updates to my code and then convert
it to an MDE and replace my FE? If so will I need to add my table links
everytime I do this?

Actually that was 3 questions....I probably have more but I figured I would
start with these.
 
Ad

Advertisements

A

Albert D.Kallal

1. If I split a secure db into a FE/BE will the BE be secure as well and
will anyone be able to open it just by clicking on it or will they need
the
workgroup to do so?

They will need to be joined to the correct workgroup to open your back end
also.
If they don't join the correct workgroup...then they cannot open the
back end.
2. If I was to convert the FE to an MDE file will I need to convert the BE
to an MDE file as well?

No, there is not much, if any advantage to converting the back end to a mde.
(when we split...all code is removed from the back end..and a mde really
only applies to a mdb with code. So, you could convert, but I can't think of
any reason, or advantage to do so. Hence, no need to convert the BE to
a mde.
3. Do I use my original mdb file to make updates to my code and then
convert
it to an MDE and replace my FE?

Yes, you continue working on your new next great version. Each user thus
receives a copy of the mde, and this is placed on EACH computer.
If so will I need to add my table links
everytime I do this?

You should not need to do this at all. Your mdb was split into two parts.
The mdb points to the back end mdb.
When you convert the mdb to a mde, the tables links are un-touched, and
continue to point to the back end mdb.

Of course, often one of the main reasons why we split is that we can make a
COPY of the back end..and link to that
during development (hey..my delete routine just ate all of the customer data
by accident!!). Since it is so risky to
test on a live data, then why not as a good habit simply make a copy of the
Back end, and link to that during development.

Then, right before deployment, you link your front end mdb to the
production back end. Then, create the mde, and then
this new mde is placed on each computer (the links will remain pointing to
your back end on the server). This scenario assumes
you have a multi-user setup. Even if you don't, the same approach is still
used....

I explain in detail about linking, and even the use of a mde in the
following article

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
 
Ad

Advertisements

G

Guest

Hi.
1. If I split a secure db into a FE/BE will the BE be secure as well

Not if you use the database splitter. When you're ready to split the
database, make a copy of the file to be the backend. You can even name it
something like MyDB_BE.mdb. Next, delete all the forms, queries, modules,
and macros from the backend, then compact it. Next, delete all the tables
from the front end and link to their counterparts in the back end. That's
the easiest way to keep both ends secure without applying security twice.
2. If I was to convert the FE to an MDE file will I need to convert the BE
to an MDE file as well?

No. Typically, the back end only contains the tables and relationships.
3. Do I use my original mdb file to make updates to my code and then convert
it to an MDE and replace my FE?

Make sure you keep a copy of the MDB file in a secure place. As a matter of
fact, it wouldn't hurt to make a couple of copies, just in case.
If so will I need to add my table links
everytime I do this?

No. Not unless you move the tables to a new file.
Actually that was 3 questions....

Actually, that was four questions, but you can ask as many questions as you
want. Generally, it's best to keep one question per post, but if they're
closely related questions then you can put several of them in the same post.
Just don't try to overwhelm the responders, because some of us will skip
long-winded questions -- since we're all volunteers, and we have a limited
amount of time available to help as many people as we can.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact info.
 

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