ADP - on each users PC?

[Vayse]

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

 

[Norman Yuan]

Yes, it is the best practice to put local copy of ADP for each user, just as
you do with *.mdb front end.

 

[Robert Morley]

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

 

[Vadim Rapp]

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

 

[aaron.kempf]

yeah this is probably the WORST usability issue facing ADP.

why does it prompt you about READ-ONLY?

 

[Vayse]

Thanks for the reply.

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

 

[PBsoft]

I would recommend the following: (1) compile it into ADE (equivalent

Which is the same as my colleague suggests.

By this, do you mean that windows create a temporary local copy, that
the user then works from?

It sounds strange to me!!!!

I see I have other replies which recommend a different method. I'll
have to think on this!

If you have time to try it, please do so then report all us.

 

[aaron.kempf]

ADP will be marginally slower across a network than from the desktop.

for this reason; I usually copy them to a local machine through a batch
file or something.

the bottom line is that ADP are 1-10mb.. where as MDB files START at
20mb and go up to a couple hundred mb.

ADP is superior-- because it's SMALLER
but it's still -- always-- going to perform faster to copy it to the
end-users desktop.

Whether you notice the difference or not? I sure can tell the
difference; but i'm just on a p4 2.0 right now.

ADP is just a vastly superior solution because it doesn't bring the
whole table to each desktop every time you run a query.

ADP is true client server and MDB is just a bunch of crap.

 

[aaron.kempf]

and again.. we're not talking about ERRORS we are talking about a
warning.

 

[Vadim Rapp]

??>> 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

 

[Baz]

yeah this is probably the WORST usability issue facing ADP.

why does it prompt you about READ-ONLY?

It isn't a usability issue at all, because you'd have to be an idiot to set
it up like this anyway.

 

[Baz]

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.

 

[aaron.kempf]

Baz;

no.. technically the answer is

"Microsoft is a bunch of ****ing idiots that can't polish a UI"

or

"Microsoft likes selling buggy-ass software so that they can sell you
an upgrade once every 2 years"

 

[Weaver]

Baz;

no.. technically the answer is

"Microsoft is a bunch of ****ing idiots that can't polish a UI"

or

"Microsoft likes selling buggy-ass software so that they can sell you
an upgrade once every 2 years"

yes posibly

 

[caracol]

ADP on each desktop

Hello @all,

ADP is faster and smaller than mdb, and you can use the interactibility of OLE DB with the MS SQL Server.

I used to copy my ADP on each desktop of the user(s) who needed it.

For this purpose I created a database with an ADP frontend which holds every local path and each PC for every user.
By clicking on a button, I'm able to declare the versions of the ADP as "old" (for the database). I can select / deselect the persons I want / don't want to get the new version.
By clicking on another button it will start to try to copy the ADP from my machine to the backuppath on the net as well as on each PC of the users I selected (or which were selected by default to to the "declaring old" function).

This works for a large number of users, computers and different databases as long as I have an account which has access to the computers (usually an enterprise admin).

You can create reports which will tell you who is working with wich database and wich PCs as well as their version.

Regards,
caracol