Run adp from network or locally

[Keith G Hicks]

I have an adp that uses sql 2000 and it runs fine when I distribute the adp
to each workstation. But it occurred to me that I could probably run this
from a network location via shortcuts on each workstation. But when I did
that I could only run from one at a time. A second workstation got a locking
error before the project even opened up. It wanted to open it read only. Is
it possible to do this or does the adp need to be distributed?

Thanks,

Keith

 

[Norman Yuan]

The "locking error" when loading the ADP from a network location just
prompts you the fact that the ADP itself is read-only (that is, the second
and later user cannot modify the ADP design, which you never want it to
happen anyway), it does not affect how ADP access the back-end SQL Server.
So, if you do not mind the annoying message box pops up, which may scare
ordinary users, then that is fine. I am not aware there is something you can
do to suppress this message box. So, place a copy of the ADP to each user's
computer would be the desired deployment method.

 

[a a r o n . k e m p f]

I personally prefer to just keep them on the network; and have a
couple copies of the ADP

APP1_Aaron.adp
APP1_Susie.adp

etc

I just think that it's a lot easier to manage them if they're all on
the network.

-Aaron

 

[bcap]

I store a master copy of the adp on a file server. Users launch the system
from a short cut on their desktop which runs a vbscript file. The file
checks whether they have a local copy of the adp, and if not it copies the
master copy to a local folder. It then launches the local copy.

That's the basic idea, it's really a LOT more sophisticated than that.
There are actually three files involved: the main master (on the file
server), a local master copy, and the local run copy. The process is thus:

Does the local master exist? If not, copy the main master to the local
master.
Is the local master older than the main master? If so, copy the main master
to the local master.
Copy the local master to the local run copy.
Launch the local run copy.

This ensures that (i) users always get a "fresh" front-end when they launch
the system, thereby eliminating problems with corruption and bloat (ii) new
versions get automatically distributed simply by replacing the main master
and (iii) file copies across the network only occur when there is a new
version.