Splitting Dbase on network

[szag via AccessMonster.com]

I am toying with the idea of splitting my dbase but have one question. Why do
you have to "distribute" the front end? Why can't that sit on the network
with the back end. The way I envision splitting is that you have a BE and FE
then if I need to make changes to the FE I have a copy that I make changes to
then replace the original FE (on the server) with the one I made changes to.
Since it is on
the server there is no distribution. Am I confused on this topic?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-multiuser/200912/1

[Tom Lake]

"szag via AccessMonster.com" <u2885@uwe> wrote in message news:a0f8f580a41d9@uwe...

> I am toying with the idea of splitting my dbase but have one question. Why do
> you have to "distribute" the front end? Why can't that sit on the network
> with the back end. The way I envision splitting is that you have a BE and FE
> then if I need to make changes to the FE I have a copy that I make changes to
> then replace the original FE (on the server) with the one I made changes to.
> Since it is on
> the server there is no distribution. Am I confused on this topic?

If the FE is on the network, then whenever you want to work on it, you have to have
all users close it and stay out of it for as long as it takes you to make changes.
If it's on each individual machine, you can make changes to your copy
whenever you want and just make a single distribution. which disrupts users less.
Also, there's less network traffic if the FEs are distributed and much less chance
of corruption.

Tom Lake

[Armen Stein]

On Tue, 22 Dec 2009 14:43:37 GMT, "szag via AccessMonster.com"
<u2885@uwe> wrote:

>I am toying with the idea of splitting my dbase but have one question. Why do
>you have to "distribute" the front end? Why can't that sit on the network
>with the back end. The way I envision splitting is that you have a BE and FE
>then if I need to make changes to the FE I have a copy that I make changes to
>then replace the original FE (on the server) with the one I made changes to.
>Since it is on
>the server there is no distribution. Am I confused on this topic?

A few reasons to distribute your front-end:

- Having multiple users in the same FE can greatly increase the
chances of corruption.

- Pulling all the FE objects (forms, reports, etc.) over the network
can slow things down.

- Replacing the master copy on the network requires kicking everyone
out.

If a simple copy routine in a BAT file doesn't work for you, check out
Tony Toews free updater:
http://autofeupdater.com/

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

[szag via AccessMonster.com]

Thanks Tom -

I guess I am still a bit confused. Lets say I wanted to add another page to a
tab control. Why couldn't I make a copy of the FE, add the tab and associated
fields while not interrupting anyone (because they are using the original),
then copy FE with the the changes I made back over the top of the original FE
when everyone is out of the FE. I know there may be better ways but isn't
this an effective way of leveraging splitting your database?

Tom Lake wrote:
>> I am toying with the idea of splitting my dbase but have one question. Why do
>> you have to "distribute" the front end? Why can't that sit on the network

>[quoted text clipped - 3 lines]

>> Since it is on
>> the server there is no distribution. Am I confused on this topic?
>
>If the FE is on the network, then whenever you want to work on it, you have to have
>all users close it and stay out of it for as long as it takes you to make changes.
>If it's on each individual machine, you can make changes to your copy
>whenever you want and just make a single distribution. which disrupts users less.
>Also, there's less network traffic if the FEs are distributed and much less chance
>of corruption.
>
>Tom Lake

--

[Armen Stein]

On Tue, 22 Dec 2009 15:57:39 GMT, "szag via AccessMonster.com"
<u2885@uwe> wrote:

>Why couldn't I make a copy of the FE, add the tab and associated
>fields while not interrupting anyone (because they are using the original),
>then copy FE with the the changes I made back over the top of the original FE
>when everyone is out of the FE.

The key statement there is "when everyone is out of the FE".

The point we're making is that by distributing it, you don't need to
kick everyone out to deploy the new version.

Plus the other reasons we've posted.

[szag via AccessMonster.com]

Thanks, helps alot. Guess I was looking at avoiding the whole distribution
process and making sure end users had updated FE's, but the advantages seem
to outweigh that one small issue.

Armen Stein wrote:
>>Why couldn't I make a copy of the FE, add the tab and associated
>>fields while not interrupting anyone (because they are using the original),
>>then copy FE with the the changes I made back over the top of the original FE
>>when everyone is out of the FE.
>
>The key statement there is "when everyone is out of the FE".
>
>The point we're making is that by distributing it, you don't need to
>kick everyone out to deploy the new version.
>
>Plus the other reasons we've posted.
>
>Armen Stein
>Microsoft Access MVP
>www.JStreetTech.com

--

[Tony Toews [MVP]]

Armen Stein <Armen...@removethisgmail.com> wrote:

>If a simple copy routine in a BAT file doesn't work for you, check out
>Tony Toews free updater:
>http://autofeupdater.com/

BTW I've recently added some options to make the initial user install
much easier. You can now email the user a URL to a shortcut on the
server which starts the initial copying of the FE to the users
workstation and creates the desktop shortcuts. It's now a matter of
a few mouse clicks and you're done.

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/

[GBA]

also - with just the most basic Windows folder sharing - set up at each
desktop..you can distribute the FE to everyone's location with a simple
copy/paste (assuming they are not in the FE at that moment in time)....from
your PC.

"szag via AccessMonster.com" wrote:

> .
>

[Tony Toews [MVP]]

GBA <G...@discussions.microsoft.com> wrote:

>also - with just the most basic Windows folder sharing - set up at each
>desktop..you can distribute the FE to everyone's location with a simple
>copy/paste (assuming they are not in the FE at that moment in time)....from
>your PC.

I would've thought that's very unlikely to be setup. And, of course,
they can't be in the app at the time. And the computer must be turned
on.