I have set up an Access database that I would like to have available to edit
across the WAN. I have tried it and it is very slow and cumbersom. Does
splitting the DB help with speed across the WAN? Or is there some other way
to improve performance when working with Access at multiple sites?
--
R. Shigley
Thermadyne

Splitting will change nothing to the speed (however, it's still a very good
idea to do so if you want to go multi-users).

For your speed problem, see
http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Robert" <(E-Mail Removed)> wrote in message
news:5D3D50B5-BFB7-434A-AA64-(E-Mail Removed)...
>I have set up an Access database that I would like to have available to
>edit
> across the WAN. I have tried it and it is very slow and cumbersom. Does
> splitting the DB help with speed across the WAN? Or is there some other
> way
> to improve performance when working with Access at multiple sites?
> --
> R. Shigley
> Thermadyne

Hi Robert,

Splitting the database into front and back ends will improve performance,
but many other things also come into play, like how close the directory is to
the route drive for the _be and it is always worth having a permanently
*connected* form open on each front end so it doesn't have to establish a
connection each time a user tries to open a form.

See http://www.granite.ab.ca/access/performancefaq.htm for more info.

hope this helps,

TonyT..

"Robert" wrote:

> I have set up an Access database that I would like to have available to edit
> across the WAN. I have tried it and it is very slow and cumbersom. Does
> splitting the DB help with speed across the WAN? Or is there some other way
> to improve performance when working with Access at multiple sites?
> --
> R. Shigley
> Thermadyne

Robert wrote:
> I have set up an Access database that I would like to have available
> to edit across the WAN. I have tried it and it is very slow and
> cumbersom. Does splitting the DB help with speed across the WAN? Or
> is there some other way to improve performance when working with
> Access at multiple sites?

Access likes to have a good solid fast LAN even when split. I would
suggest that if you have a critical application that you don't try and use a
WAN without a very solid backup provision. This is one of the few situation
I would recommend considering another solution.

Yes Aaron, there are times I recommend other solutions. :-)


--
Joseph Meehan

Dia 's Muire duit

Oops, I've made a small error here: splitting the file will slightly
increase the performance because the forms, reports and modules won't have
to be transferred over the wire. However, the (lack of) speed for accessing
the data will remain the same.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:(E-Mail Removed)...
> Splitting will change nothing to the speed (however, it's still a very
> good idea to do so if you want to go multi-users).
>
> For your speed problem, see
> http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Robert" <(E-Mail Removed)> wrote in message
> news:5D3D50B5-BFB7-434A-AA64-(E-Mail Removed)...
>>I have set up an Access database that I would like to have available to
>>edit
>> across the WAN. I have tried it and it is very slow and cumbersom. Does
>> splitting the DB help with speed across the WAN? Or is there some other
>> way
>> to improve performance when working with Access at multiple sites?
>> --
>> R. Shigley
>> Thermadyne
>
>

Most of the WAN traffic would not be 'write' activity, but read only via Data
Access Page. Most likely it would be only 3 users writing data. Would you
still recommend an alternate solution in that situation?
--
R. Shigley
Thermadyne


"Joseph Meehan" wrote:

> Robert wrote:
> > I have set up an Access database that I would like to have available
> > to edit across the WAN. I have tried it and it is very slow and
> > cumbersom. Does splitting the DB help with speed across the WAN? Or
> > is there some other way to improve performance when working with
> > Access at multiple sites?
>
> Access likes to have a good solid fast LAN even when split. I would
> suggest that if you have a critical application that you don't try and use a
> WAN without a very solid backup provision. This is one of the few situation
> I would recommend considering another solution.
>
> Yes Aaron, there are times I recommend other solutions. :-)
>
>
> --
> Joseph Meehan
>
> Dia 's Muire duit
>
>
>
>

Thanks for the input.
--
R. Shigley
Thermadyne


"Sylvain Lafontaine" wrote:

> Oops, I've made a small error here: splitting the file will slightly
> increase the performance because the forms, reports and modules won't have
> to be transferred over the wire. However, the (lack of) speed for accessing
> the data will remain the same.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
> wrote in message news:(E-Mail Removed)...
> > Splitting will change nothing to the speed (however, it's still a very
> > good idea to do so if you want to go multi-users).
> >
> > For your speed problem, see
> > http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html
> >
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> >
> >
> > "Robert" <(E-Mail Removed)> wrote in message
> > news:5D3D50B5-BFB7-434A-AA64-(E-Mail Removed)...
> >>I have set up an Access database that I would like to have available to
> >>edit
> >> across the WAN. I have tried it and it is very slow and cumbersom. Does
> >> splitting the DB help with speed across the WAN? Or is there some other
> >> way
> >> to improve performance when working with Access at multiple sites?
> >> --
> >> R. Shigley
> >> Thermadyne
> >
> >
>
>
>

Thanks for the input.
--
R. Shigley
Thermadyne


"TonyT" wrote:

> Hi Robert,
>
> Splitting the database into front and back ends will improve performance,
> but many other things also come into play, like how close the directory is to
> the route drive for the _be and it is always worth having a permanently
> *connected* form open on each front end so it doesn't have to establish a
> connection each time a user tries to open a form.
>
> See http://www.granite.ab.ca/access/performancefaq.htm for more info.
>
> hope this helps,
>
> TonyT..
>
> "Robert" wrote:
>
> > I have set up an Access database that I would like to have available to edit
> > across the WAN. I have tried it and it is very slow and cumbersom. Does
> > splitting the DB help with speed across the WAN? Or is there some other way
> > to improve performance when working with Access at multiple sites?
> > --
> > R. Shigley
> > Thermadyne

Yes. Access databases are very sensitive to network problems (they've been
likened to the miner's canary for networks!).

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)


"Robert" <(E-Mail Removed)> wrote in message
news:8344B55A-BE9A-4DF0-9606-(E-Mail Removed)...
> Most of the WAN traffic would not be 'write' activity, but read only via
> Data
> Access Page. Most likely it would be only 3 users writing data. Would you
> still recommend an alternate solution in that situation?
> --
> R. Shigley
> Thermadyne
>
>
> "Joseph Meehan" wrote:
>
>> Robert wrote:
>> > I have set up an Access database that I would like to have available
>> > to edit across the WAN. I have tried it and it is very slow and
>> > cumbersom. Does splitting the DB help with speed across the WAN? Or
>> > is there some other way to improve performance when working with
>> > Access at multiple sites?
>>
>> Access likes to have a good solid fast LAN even when split. I would
>> suggest that if you have a critical application that you don't try and
>> use a
>> WAN without a very solid backup provision. This is one of the few
>> situation
>> I would recommend considering another solution.
>>
>> Yes Aaron, there are times I recommend other solutions. :-)
>>
>>
>> --
>> Joseph Meehan
>>
>> Dia 's Muire duit
>>
>>
>>
>>

Actually, I wouldn't recommend DAPs, either. They are "deprecated" in Access
2007... it will support running the ones you already have, but you can't
develop new ones or maintain existing ones (for maintenance, you'll need to
maintain a copy of Access 2003 or earlier). They had limitations that kept
them from gaining "earthshaking acceptance."

WAN or Internet connections just are not adequate for a file-server database
such as Jet. Access uses the remote DB file just as it would a file on a
local hard drive; that is, it doesn't pull everything across the network,
but it pulls a LOT across the network and does all the data extraction,
manipulation, etc. on the user's machine.

There are solutions you can use with a WAN... such as Microsoft Terminal
Server, or a genuine web-server based application done in classic ASP or
ASP.NET, and some steps in between.

Larry Linson
Microsoft Access MVP


"Robert" <(E-Mail Removed)> wrote in message
news:8344B55A-BE9A-4DF0-9606-(E-Mail Removed)...
> Most of the WAN traffic would not be 'write' activity, but read only via
> Data
> Access Page. Most likely it would be only 3 users writing data. Would you
> still recommend an alternate solution in that situation?
> --
> R. Shigley
> Thermadyne
>
>
> "Joseph Meehan" wrote:
>
>> Robert wrote:
>> > I have set up an Access database that I would like to have available
>> > to edit across the WAN. I have tried it and it is very slow and
>> > cumbersom. Does splitting the DB help with speed across the WAN? Or
>> > is there some other way to improve performance when working with
>> > Access at multiple sites?
>>
>> Access likes to have a good solid fast LAN even when split. I would
>> suggest that if you have a critical application that you don't try and
>> use a
>> WAN without a very solid backup provision. This is one of the few
>> situation
>> I would recommend considering another solution.
>>
>> Yes Aaron, there are times I recommend other solutions. :-)
>>
>>
>> --
>> Joseph Meehan
>>
>> Dia 's Muire duit
>>
>>
>>
>>