|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
Hi
When I used mdbs, I always put a local front end database on each PC, with
the data on the server.
I'm new to ADPs, but I'm guessing that the same idea applies. A workmate is
suggesting that one ADP on the server will do the job.
Now, I thought one of the reasons for storing the frontend locally, was to
stop the forms and reports layout date being transferred over the network.
Whats the recommended practice for ADPs?
Thanks
Diarmuid
|
|
Yes, it is the best practice to put local copy of ADP for each user, just as
you do with *.mdb front end.
"Vayse" <vayse[ at ]deadspam.com> wrote in message
news:u60cCc7tGHA.4472[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Hi
> When I used mdbs, I always put a local front end database on each PC, with
> the data on the server.
>
> I'm new to ADPs, but I'm guessing that the same idea applies. A workmate
> is suggesting that one ADP on the server will do the job.
> Now, I thought one of the reasons for storing the frontend locally, was to
> stop the forms and reports layout date being transferred over the network.
>
> Whats the recommended practice for ADPs?
>
> Thanks
> Diarmuid
>
>
|
|
And, in fact, it's even more recommended with ADP's, as a shared ADP will
give you errors about being locked, where if I remember correctly, and MDB
won't.
Rob
"Norman Yuan" <NotReal[ at ]NotReal.not> wrote in message
news:%23y7lv48tGHA.2260[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Yes, it is the best practice to put local copy of ADP for each user, just
> as you do with *.mdb front end.
|
|
V> When I used mdbs, I always put a local front end database on each PC,
V> with the data on the server.
V> I'm new to ADPs, but I'm guessing that the same idea applies. A workmate
V> is suggesting that one ADP on the server will do the job.
V> Now, I thought one of the reasons for storing the frontend locally, was
V> to stop the forms and reports layout date being transferred over the
V> network.
No, it certainly won't stop that. Regardless of where the file is started
from, it runs on user workstation. When it's launched, it gets copied from
the server.
I would recommend the following: (1) compile it into ADE (equivalent of
mde); (2) put on server and make it there read-only.
Microsoft recommends using local copy, however, Access has a bug that
prompts making the ade read-only. The bug is in automatic quiet resaving
forms along with applied filter, which makes them unusable when used with
opening criteria. So it's better to disalllow resaving the adp/ade by making
it read-only, in which case it can live on server.
With read-only adp/ade, full Access will display a warning on starting, but
I found it to be lesser evil than the consequences of quiet resaving. Access
Runtime does not display the warning.
Vadim Rapp
|
|
Thanks for the reply.
"Vadim Rapp" <vr[ at ]myrealbox.nospam.com> wrote in message
news:uBUFlKJuGHA.3964[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text] >s<nip>
> I would recommend the following: (1) compile it into ADE (equivalent of
> mde); (2) put on server and make it there read-only.
>
Which is the same as my colleague suggests.
> Regardless of where the file is started
>from, it runs on user workstation. When it's launched, it gets copied from
>the server.
By this, do you mean that windows create a temporary local copy, that the
user then works from?
I see I have other replies which recommend a different method. I'll have to
think on this!
Regards
Diarmuid
|
|
??>> Regardless of where the file is started
??>> from, it runs on user workstation. When it's launched, it gets copied
??>> from the server.
V> By this, do you mean that windows create a temporary local copy, that
V> the user then works from?
No, I mean that the file is being read from the network, along with all its
forms and reports and everything else. Once the ADP file is launched, it's
in the workstation memory, so there's no further difference.
Since this is adp newsgroup, if the file is adp, it means that the data
comes from the database server - again, does not matter where the frontend
was launched from.
Vadim Rapp
|
|
"Vayse" <vayse[ at ]deadspam.com> wrote in message
news:u60cCc7tGHA.4472[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text] > Hi
> When I used mdbs, I always put a local front end database on each PC, with
> the data on the server.
>
> I'm new to ADPs, but I'm guessing that the same idea applies. A workmate
is
> suggesting that one ADP on the server will do the job.
> Now, I thought one of the reasons for storing the frontend locally, was to
> stop the forms and reports layout date being transferred over the network.
>
> Whats the recommended practice for ADPs?
>
> Thanks
> Diarmuid
>
>
I always set up adp systems as follows:
"main" master copy of the adp file on a server
"local" master copy of the adp file on each workstation
"local" run copy of the adp file on each workstation (this is the one that
gets opened by the user).
What the users actually run when they launch the system is a vbscript which:
1. compares the last-modified timestamp on the main master and local
master
2. if they are different, copies the main master to replace the local
master
3. copies the local master to replace the run copy
4. launches the run copy.
This ensures that (i) every user opens a nice, clean LOCAL adp every time
they
launch the system (ii) updates to the adp get automatically distributed, all
you have to do is to update the main master and (iii) the file copy over the
network only occurs when it is really needed i.e. when the main master has
been updated.
|
|
|