Split database questions ?

[steve]

I have never split a data base but have read several articles on the
web and I think I understand how to do it.

A couple of questions,

1. Do I load the font end onto all the computers that I want to use
the database or do they just go to one central place and everybody
clicks the same front end in one central location. (IM asuming you
load it on all the computers.)

2. When I want to change the database, that is change a form on the
front end or add a new form and table to the frontend backend, how do
I do this? Where do I do this ? Do I open the front end and act like
it is a normal access db ?? I don't understand where or how I do
further development?

3. If the answer to 1. is put on all desktops, Im asuming that if I
change the front end I have to put this new changed frontend on on all
the desktops overwriting the previous.

4. I have seen several commens regarding turning your database (Front
end I guess) into a .MDE file, an uneditable file. Is this required
for the front end back end process to work. Or is it just a wise
precaution that should be done to stop end users from fiddling with
things.

Thank you for your answers.

Regards
Steve
7willie

 

[Al Campagna]

Steve,
1. BackEnd on the server, and FrontEnd on each PC is the preferred method. You can also
have both on the server, but for a large quantity of users, and a large application,
performance could suffer. No problem with trying either method.
2. Ne tables and fields will have to be updated in the BE, and new forms, reports etc..
updated on the FE. New tables will also need to be linked.
3. Yes. You could build a .bat file that automatically goes out on the network, and
replaces everyone's FE... when needed.
4. I'm not sure that you'll see any performance difference between MDB and MDE. It's more
of a security issue than one of performance. Again, you're best bet is to test hop each
setup.
--
hth
Al Campagna . Candia Computer Consulting . Candia, NH USA
Microsoft Access MVP
http://home.comcast.net/~cccsolutions

"Find a job that you love, and you'll never work a day in your life."

 

[Allen Browne]

Answers embedded.

--
Allen Browne - Microsoft MVP. Perth, Western Australia

Reply to group, rather than allenbrowne at mvps dot org.

I have never split a data base but have read several articles on the
web and I think I understand how to do it.

A couple of questions,

1. Do I load the font end onto all the computers that I want to use
the database or do they just go to one central place and everybody
clicks the same front end in one central location. (IM asuming you
load it on all the computers.)

Yes: a separate front end for each user.

2. When I want to change the database, that is change a form on the
front end or add a new form and table to the frontend backend, how do
I do this? Where do I do this ? Do I open the front end and act like
it is a normal access db ?? I don't understand where or how I do
further development?

There is one front end which is the development copy. You work on that,
adding forms, writing code, testing, debugging, until you have completed the
next version. Then you distribute that copy to everyone.

3. If the answer to 1. is put on all desktops, Im asuming that if I
change the front end I have to put this new changed frontend on on all
the desktops overwriting the previous.

Correct. Each workstation will have it's own copy, typically on its own hard
drive. Any folder that suits you.

To update it, you can write a logon script, share the workstation's folders
so you can copy the new versions there, or use a utility such as this:
http://www.granite.ab.ca/access/autofe.htm

4. I have seen several commens regarding turning your database (Front
end I guess) into a .MDE file, an uneditable file. Is this required
for the front end back end process to work. Or is it just a wise
precaution that should be done to stop end users from fiddling with
things.

Normally the front end is an MDE, though this is not required.

The advantages of the MDE include:
- Users can't fiddle with the code, or modify the forms/reports.
- The code cannot accidentally decompile (versioning problems.)

 

[steve]

There is one front end which is the development copy. You work on that,
adding forms, writing code, testing, debugging, until you have completed the
next version. Then you distribute that copy to everyone.

Thank you, all the answers make sense.

On the develpment issue...
Im not sure how you do this. If I create a new table on the FE, make
new forms etc. then how do I move the table and link to the BE. Of
course I can open the BE and import it from the FE, that is not a
problem I dont think. But How do I set up he link, that the table
splitting program does so easily. I tried looking at properties of the
->table fromt the FE but it doesnt seem to have anything that I can
edit.

 

[Peter Hibbs]

Steve

To add fields and tables to the back end from code in the front end
have a look at :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE Update Utility.mdb'

This code makes it very easy to update the back-end file, especially
if your database is being used by someone at a remote location.

Peter Hibbs.

 

[steve]

Steve

To add fields and tables to the back end from code in the front end
have a look at :-

http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='BE%2...

This code makes it very easy to update the back-end file, especially
if your database is being used by someone at a remote location.

Peter Hibbs.





- Show quoted text -

How would you do it "not programiclly". I want to pass this info onto
a person who is not a programer. If you were just a smuck access user
how would you acchieve this .

Thank.

 

[Peter Hibbs]

Steve

If you mean how would you allow a non-programmer to change the design
of the back end file then I would NOT let a 'smuck' anywhere near the
file, they could do untold damage to your valuable data. That is the
whole point of the Back End Update code, it allows you, the developer,
to change the table schema without involving the client. If you mean
something else then post back with more details.

Peter Hibbs.

 

[steve]

Steve

If you mean how would you allow a non-programmer to change the design
of the back end file then I would NOT let a 'smuck' anywhere near the
file, they could do untold damage to your valuable data. That is the
whole point of the Back End Update code, it allows you, the developer,
to change the table schema without involving the client. If you mean
something else then post back with more details.

Peter Hibbs.





- Show quoted text -

Well perhaps I overstated the smuck factor. I have done some
programing but have never done this. But I guess I would like to know
how to do it in a pedestrian fashion before I do it through
programing. Also the person I am passing this on to has writen
databases but not done any programing. It is for a very small
organization.I dont want to give him anything that he has never done
before. As far as wrecking the database. Thats up to him, I only want
to show him the options.
Im still not sure how you would do this simly using standard Access
tools.

Regards
Steve

 

[Allen Browne]

A savvy Access user can use the Linked Table manager to relink the tables to
the new location. It's on the Tools menu.

What I personally do is to check the links on startup, and if the tables are
not there, relink. The core code to loop through the TableDefs and set the
Connect property is here:
Attached tables: reconnect on start up
at:
http://allenbrowne.com/ser-13.html

That example assumes the back end and front end are in the same folder.
That's not usually the case, so you want to pop up the Windows File Open
dialog, and let the user find the server and folder where the data file
really is. Dev Ashish's solution does that:
http://www.mvps.org/access/tables/tbl0009.htm

Another alternative is to use the equivalent of an INI file to tell the
updated front end where to look for the back end. Tony Toews's solution does
that:
http://www.granite.ab.ca/access/autofe.htm

 

[steve]

A savvy Access user can use the Linked Table manager to relink the tables to
the new location. It's on the Tools menu.

Wow a whole basket of answers. Thanks. I will do some playing and see
which is most apropriate.
The linked table option this doesnt move the tables I asume, Im
guessing you just create them in the BE and then link them to the
front then start building forms and doing the development.

Regards