|
 |
access thread: Front-End
Message #1 by "George Oro" <george@c...> on Mon, 29 Jul 2002 10:24:13 +0400
|
|
Hi Guys,
Just a thought...
I have a multi-user db and of course my back-end is installed on the server. I'm just wondering where is the best place (PC) to
installed my front-end, on the server or on each client?
If there's some difference between installing the front-end on the server or on each client please explain.
Any suggestion or other idea is highly appreciated.
Cheers,
George
Message #2 by "Vlad VRA09 Rakic" <vrakic@q...> on Mon, 29 Jul 2002 16:44:40 +1000
|
|
George,
I have both front and back end database sitting on a server and works fine.
Having a copy of front end on each user's PC will make it more difficult
for you to maintain - every time you update the front end you'll have to
distribute copies to each user.
Regards,
Vlad
*******************Confidentiality and Privilege Notice*******************
This email is intended only to be read or used by the addressee.
It is confidential and may contain legally privileged information.
If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you
may not copy or deliver this message to anyone, and you should
destroy this message and kindly notify the sender by reply email.
Confidentiality and legal privilege are not waived or lost by
reason of mistaken delivery to you.
Qantas Airways Limited
ABN 16 009 661 901
Visit Qantas online at http://www.qantas.com.au
Message #3 by braxis@b... on Mon, 29 Jul 2002 08:17:07 +0100 (BST)
|
|
On the other hand...
You will be loosing one of the main advantages of splitting your database - reduced network traffic.
If you place the front end on the server, every time the user changes form, or uses a function in a new code module, it has to be
dragged over the network from the server.
Brian
> from: Vlad VRA09 Rakic <vrakic@q...>
> date: Mon, 29 Jul 2002 07:44:40
> to: access@p...
> subject: Re: [access] Re: Front-End
>
>
> George,
>
> I have both front and back end database sitting on a server and works fine.
> Having a copy of front end on each user's PC will make it more difficult
> for you to maintain - every time you update the front end you'll have to
> distribute copies to each user.
>
>
> Regards,
>
> Vlad
>
>
>
> *******************Confidentiality and Privilege Notice*******************
>
> This email is intended only to be read or used by the addressee.
> It is confidential and may contain legally privileged information.
> If you are not the addressee indicated in this message (or
> responsible for delivery of the message to such person), you
> may not copy or deliver this message to anyone, and you should
> destroy this message and kindly notify the sender by reply email.
> Confidentiality and legal privilege are not waived or lost by
> reason of mistaken delivery to you.
>
> Qantas Airways Limited
> ABN 16 009 661 901
>
> Visit Qantas online at http://www.qantas.com.au
>
>
Message #4 by "Haslett, Andrew" <andrew.haslett@i...> on Mon, 29 Jul 2002 17:13:10 +0930
|
|
ALWAYS place the client on each users machine. There are a number of
reasons for this listed in previous threads, among which are network traffic
/ speed / corruption etc.
Updating the client copies is not difficult at all. In our network
environment we have a common start menu script which checks to see if the
latest version is already on the clients machine, if not, copy over it, then
run it. About 5 lines of code.
Cheers,
Andrew
-----Original Message-----
From: Vlad VRA09 Rakic [mailto:vrakic@q...]
Sent: Monday, 29 July 2002 4:15 PM
To: Access
Subject: [access] Re: Front-End
George,
I have both front and back end database sitting on a server and works fine.
Having a copy of front end on each user's PC will make it more difficult
for you to maintain - every time you update the front end you'll have to
distribute copies to each user.
Regards,
Vlad
*******************Confidentiality and Privilege Notice*******************
This email is intended only to be read or used by the addressee.
It is confidential and may contain legally privileged information.
If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you
may not copy or deliver this message to anyone, and you should
destroy this message and kindly notify the sender by reply email.
Confidentiality and legal privilege are not waived or lost by
reason of mistaken delivery to you.
Qantas Airways Limited
ABN 16 009 661 901
Visit Qantas online at http://www.qantas.com.au
Message #5 by "George Oro" <george@c...> on Mon, 29 Jul 2002 11:58:26 +0400
|
|
Andrew, Vlad, Brian,
Thanks a lot for your tips!!! majority always win.
Cheers,
George
-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Monday, July 29, 2002 11:43 AM
To: Access
Subject: [access] Re: Front-End
ALWAYS place the client on each users machine. There are a number of
reasons for this listed in previous threads, among which are network traffic
/ speed / corruption etc.
Updating the client copies is not difficult at all. In our network
environment we have a common start menu script which checks to see if the
latest version is already on the clients machine, if not, copy over it, then
run it. About 5 lines of code.
Cheers,
Andrew
-----Original Message-----
From: Vlad VRA09 Rakic [mailto:vrakic@q...]
Sent: Monday, 29 July 2002 4:15 PM
To: Access
Subject: [access] Re: Front-End
George,
I have both front and back end database sitting on a server and works fine.
Having a copy of front end on each user's PC will make it more difficult
for you to maintain - every time you update the front end you'll have to
distribute copies to each user.
Regards,
Vlad
*******************Confidentiality and Privilege Notice*******************
This email is intended only to be read or used by the addressee.
It is confidential and may contain legally privileged information.
If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you
may not copy or deliver this message to anyone, and you should
destroy this message and kindly notify the sender by reply email.
Confidentiality and legal privilege are not waived or lost by
reason of mistaken delivery to you.
Qantas Airways Limited
ABN 16 009 661 901
Visit Qantas online at http://www.qantas.com.au
Message #6 by jose.johnson@j... on Mon, 29 Jul 2002 17:51:46 +0900
|
|
I also have the same thought of Brain
Updating to the client is not a big issue. Also the revisions are very
less
Network traffic is the one to be prioritized.
Best Regards
braxis@b...
.com To: access@p...
cc:
07/29/2002 04:17 Subject: [access] Re: Front-End
PM
Please respond to
access
On the other hand...
You will be loosing one of the main advantages of splitting your database -
reduced network traffic.
If you place the front end on the server, every time the user changes form,
or uses a function in a new code module, it has to be dragged over the
network from the server.
Brian
> from: Vlad VRA09 Rakic <vrakic@q...>
> date: Mon, 29 Jul 2002 07:44:40
> to: access@p...
> subject: Re: [access] Re: Front-End
>
>
> George,
>
> I have both front and back end database sitting on a server and works
fine.
> Having a copy of front end on each user's PC will make it more difficult
> for you to maintain - every time you update the front end you'll have to
> distribute copies to each user.
>
>
> Regards,
>
> Vlad
>
>
>
> *******************Confidentiality and Privilege
Notice*******************
>
> This email is intended only to be read or used by the addressee.
> It is confidential and may contain legally privileged information.
> If you are not the addressee indicated in this message (or
> responsible for delivery of the message to such person), you
> may not copy or deliver this message to anyone, and you should
> destroy this message and kindly notify the sender by reply email.
> Confidentiality and legal privilege are not waived or lost by
> reason of mistaken delivery to you.
>
> Qantas Airways Limited
> ABN 16 009 661 901
>
> Visit Qantas online at http://www.qantas.com.au
>
>
Message #7 by Arthur Maloney <ArthurMaloney@s...> on Mon, 29 Jul 2002 09:50:28 +0100
|
|
Hello George,
Monday, July 29, 2002, 7:24:13 AM, you wrote:
GO> I have a multi-user db and of course my back-end is installed on the server. I'm just wondering where is the best place (PC)
to
GO> installed my front-end, on the server or on each client?
I usually compile the front end as an mde
I also tend to put this on the server with a desktop shortcut on the
user's machine.
Depending on PC Quality, Op Sys, Memory and how the client network
works.
It is usually good enough. It has the advantage that all users pickup
any changes to the mde file.
More recently because of changes to neworks arising because of microsoft
created security issues I tend to place it on the local PC and use n
installer for that purpuse. A changed mde is e-mailed to each user as
an installer package. the front end works quicker on the users PC but
each PC most be visited.
--
Best regards,
Arthur mailto:ArthurMaloney@s...
Message #8 by "George Oro" <george@c...> on Mon, 29 Jul 2002 16:14:13 +0400
|
|
Arthur, Jose,
Thanks for your additional tips...
Cheers,
George
-----Original Message-----
From: Arthur Maloney [mailto:ArthurMaloney@s...]
Sent: Monday, July 29, 2002 12:50 PM
To: Access
Subject: [access] Re: Front-End
Hello George,
Monday, July 29, 2002, 7:24:13 AM, you wrote:
GO> I have a multi-user db and of course my back-end is installed on the server. I'm just wondering where is the best place (PC)
to
GO> installed my front-end, on the server or on each client?
I usually compile the front end as an mde
I also tend to put this on the server with a desktop shortcut on the
user's machine.
Depending on PC Quality, Op Sys, Memory and how the client network
works.
It is usually good enough. It has the advantage that all users pickup
any changes to the mde file.
More recently because of changes to neworks arising because of microsoft
created security issues I tend to place it on the local PC and use n
installer for that purpuse. A changed mde is e-mailed to each user as
an installer package. the front end works quicker on the users PC but
each PC most be visited.
--
Best regards,
Arthur mailto:ArthurMaloney@s...
Message #9 by "Jeff Graves" <jeff@i...> on Mon, 29 Jul 2002 09:17:27 -0400
|
|
And...if you turn it into a windows installer package you can use
Group Policy on 2K to make sure it is seamlessly maintained on your
clients.
Jeff Graves
Customer Support Engineer
Image Source, Inc.
10 Mill Street
Bellingham, MA 02019
jeff@i... - Email
xxx.xxx.xxxx X31 - Phone
xxx.xxx.xxxx - Fax
-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Monday, July 29, 2002 3:43 AM
To: Access
Subject: [access] Re: Front-End
ALWAYS place the client on each users machine. There are a number of
reasons for this listed in previous threads, among which are network
traffic
/ speed / corruption etc.
Updating the client copies is not difficult at all. In our network
environment we have a common start menu script which checks to see if
the
latest version is already on the clients machine, if not, copy over
it, then
run it. About 5 lines of code.
Cheers,
Andrew
-----Original Message-----
From: Vlad VRA09 Rakic [mailto:vrakic@q...]
Sent: Monday, 29 July 2002 4:15 PM
To: Access
Subject: [access] Re: Front-End
George,
I have both front and back end database sitting on a server and works
fine.
Having a copy of front end on each user's PC will make it more
difficult
for you to maintain - every time you update the front end you'll have
to
distribute copies to each user.
Regards,
Vlad
*******************Confidentiality and Privilege
Notice*******************
This email is intended only to be read or used by the addressee.
It is confidential and may contain legally privileged information.
If you are not the addressee indicated in this message (or
responsible for delivery of the message to such person), you
may not copy or deliver this message to anyone, and you should
destroy this message and kindly notify the sender by reply email.
Confidentiality and legal privilege are not waived or lost by
reason of mistaken delivery to you.
Qantas Airways Limited
ABN 16 009 661 901
Visit Qantas online at http://www.qantas.com.au
Message #10 by PStreeter@C... on Mon, 29 Jul 2002 8:58:12 CST
|
|
Andrew, would you post that script please. I have been trying to figure
something like that out and haven't succeeded yet. I suspect that
others may find it useful too.
Paul
On Mon, 29 Jul 2002 17:13:10 +0930 "Haslett, Andrew" wrote:
> ALWAYS place the client on each users machine. There are a number of
> reasons for this listed in previous threads, among which are network
> traffic
> / speed / corruption etc.
>
> Updating the client copies is not difficult at all. In our network
> environment we have a common start menu script which checks to see if the
> latest version is already on the clients machine, if not, copy over
> it, then
> run it. About 5 lines of code.
>
> Cheers,
> Andrew
>
> -----Original Message-----
> From: Vlad VRA09 Rakic [mailto:vrakic@q...]
> Sent: Monday, 29 July 2002 4:15 PM
> To: Access
> Subject: [access] Re: Front-End
>
>
>
> George,
>
> I have both front and back end database sitting on a server and works
> fine.
> Having a copy of front end on each user's PC will make it more difficult
> for you to maintain - every time you update the front end you'll have to
> distribute copies to each user.
>
>
> Regards,
>
> Vlad
>
Message #11 by "Haslett, Andrew" <andrew.haslett@i...> on Tue, 30 Jul 2002 08:50:44 +0930
|
|
Sure:
(I've added an asterix to the start of each line in case of wrapping)
***********************************************
*@echo off
*if not exist "c:\Documents and Settings\All Users\Data\MyDB_V1.mde" goto
getdb:
goto startdb
:getdb
*md "c:\Documents and Settings\All Users\Data" >nul
*del "c:\Documents and Settings\All Users\Data\MyDB_V*.mde" >nul
*copy l:\master\MyDB_V1.mde "c:\Documents and Settings\All Users\Data" >nul
*:startdb
*"c:\program files\microsoft office\office\msaccess.exe" "c:\Documents and
Settings\All Users\Data\MyDB_V1.mde"
**********************************************
The database in this example is obviously called MYDB_V1.mde. When I create
a new version, following conventions, it will be called v1.1 or v2 etc, so
we simply change the name in the script.
HTH,
Andrew
-----Original Message-----
From: PStreeter@C...
[mailto:PStreeter@C...]
Sent: Tuesday, 30 July 2002 12:28 AM
To: Access
Subject: [access] Re: Front-End
Andrew, would you post that script please. I have been trying to figure
something like that out and haven't succeeded yet. I suspect that
others may find it useful too.
Paul
On Mon, 29 Jul 2002 17:13:10 +0930 "Haslett, Andrew" wrote:
> ALWAYS place the client on each users machine. There are a number of
> reasons for this listed in previous threads, among which are network
> traffic
> / speed / corruption etc.
>
> Updating the client copies is not difficult at all. In our network
> environment we have a common start menu script which checks to see if the
> latest version is already on the clients machine, if not, copy over
> it, then
> run it. About 5 lines of code.
>
> Cheers,
> Andrew
>
> -----Original Message-----
> From: Vlad VRA09 Rakic [mailto:vrakic@q...]
> Sent: Monday, 29 July 2002 4:15 PM
> To: Access
> Subject: [access] Re: Front-End
>
>
>
> George,
>
> I have both front and back end database sitting on a server and works
> fine.
> Having a copy of front end on each user's PC will make it more difficult
> for you to maintain - every time you update the front end you'll have to
> distribute copies to each user.
>
>
> Regards,
>
> Vlad
>
Message #12 by "Haslett, Andrew" <andrew.haslett@i...> on Tue, 30 Jul 2002 09:41:24 +0930
|
|
Sorry, I missed a couple of asterics:
***********************************************
*@echo off
*if not exist "c:\Documents and Settings\All Users\Data\MyDB_V1.mde" goto
getdb:
*goto startdb
*:getdb
*md "c:\Documents and Settings\All Users\Data" >nul
*del "c:\Documents and Settings\All Users\Data\MyDB_V*.mde" >nul
*copy l:\master\MyDB_V1.mde "c:\Documents and Settings\All Users\Data" >nul
*:startdb
*"c:\program files\microsoft office\office\msaccess.exe" "c:\Documents and
Settings\All Users\Data\MyDB_V1.mde"
**********************************************
-----Original Message-----
From: Haslett, Andrew [mailto:andrew.haslett@i...]
Sent: Tuesday, 30 July 2002 8:51 AM
To: Access
Subject: [access] Re: Front-End
Sure:
(I've added an asterix to the start of each line in case of wrapping)
***********************************************
*@echo off
*if not exist "c:\Documents and Settings\All Users\Data\MyDB_V1.mde" goto
getdb:
goto startdb
:getdb
*md "c:\Documents and Settings\All Users\Data" >nul
*del "c:\Documents and Settings\All Users\Data\MyDB_V*.mde" >nul
*copy l:\master\MyDB_V1.mde "c:\Documents and Settings\All Users\Data" >nul
*:startdb
*"c:\program files\microsoft office\office\msaccess.exe" "c:\Documents and
Settings\All Users\Data\MyDB_V1.mde"
**********************************************
The database in this example is obviously called MYDB_V1.mde. When I create
a new version, following conventions, it will be called v1.1 or v2 etc, so
we simply change the name in the script.
HTH,
Andrew
-----Original Message-----
From: PStreeter@C...
[mailto:PStreeter@C...]
Sent: Tuesday, 30 July 2002 12:28 AM
To: Access
Subject: [access] Re: Front-End
Andrew, would you post that script please. I have been trying to figure
something like that out and haven't succeeded yet. I suspect that
others may find it useful too.
Paul
On Mon, 29 Jul 2002 17:13:10 +0930 "Haslett, Andrew" wrote:
> ALWAYS place the client on each users machine. There are a number of
> reasons for this listed in previous threads, among which are network
> traffic
> / speed / corruption etc.
>
> Updating the client copies is not difficult at all. In our network
> environment we have a common start menu script which checks to see if the
> latest version is already on the clients machine, if not, copy over
> it, then
> run it. About 5 lines of code.
>
> Cheers,
> Andrew
>
> -----Original Message-----
> From: Vlad VRA09 Rakic [mailto:vrakic@q...]
> Sent: Monday, 29 July 2002 4:15 PM
> To: Access
> Subject: [access] Re: Front-End
>
>
>
> George,
>
> I have both front and back end database sitting on a server and works
> fine.
> Having a copy of front end on each user's PC will make it more difficult
> for you to maintain - every time you update the front end you'll have to
> distribute copies to each user.
>
>
> Regards,
>
> Vlad
>
|
|
|
View Cart
