Multiuser ADP

Why can't you just let every user have his own copy?

If I distribute a copy to each and every user, the administration grows.

fx I will need to track all the copies whenever they need to be updated or the database is migrated to another server aso.  Just telling the users that they need a new copy or mailing it to them does not ensure that they actually do it (and having a version check in each project is cumbersome too).

My best workaround is a simple batch file that copies the network-adp file into the local temp folder and executes it from there. But I would like to do without that :-)

It's a common problem - alså with .mdb's.
Several of my clients simply have all the users copy the file every morning through the logonscript. If the .adp is very big, this can be a bad solution.

It is also possible to have the .adp-file check if there are any new versions on a specific location. If so, the file will automaticly copy itself to the users harddisk while the user sees a splash-screen telling them about the update.
I have the code made for .mdb, but I am sure it can be done with a .adp too.

Another solution is to have the .adp-file check if it is the latest version. If not, the user will have to activate a batchfile (copying the file to the harddisk) before the application will start.

ThomasJepsen - det

ThomasJepsen, sorry that is the solution I allready have - what I hope for is a solution that allows one to open an ADP in "share mode".

Allright, then the answer is NO....you can't!

(and please don't reject my answer until someone else gives you another solution or tells you that it is possible)

Somebody (terry) told me it was possible, thats why I opened this question...

Jeg har muligvis hørt om en løsning engang, men mener at det gav en masse problemer med performance samt ustabil miljø.

Men lad os høre, hvad Terry-drengen har af forslag :o)

(Hvorfor var det, at vi skrev på engelsk?)

Thja... Terry skriver altid på engelsk, så derfor lagde jeg ud med det - ved faktisk ikke hvor meget dansk han forstår...

Han forstår det hele (men skriver det bare ikke så godt) Hvordan tror du ellers han har kunnet opnå så mange point? Det er trods alt de færreste spørgsmål, som er på engelsk ;o)

Jeg kan ikke se det store problem i at skulle distribuere en kopi til hver brugers homedir på en server.
Jeg har et script der køres af vores filserver hver nat som kopierer en kopi af diverse databaser ud til brugernes homedir. Hvis der er en ny bruger der skal have adgang til en db, laver jeg bare en ny linie i det script og så har han/hun adgang næste morgen.
For at begrænse trafikken, har jeg så lavet et check på om en given .txt fil findes på serveren. Hvis den gør det, stopper scriptet uden at kopiere.
Når man har ændret i en db, slettes denne txt fil manuelt og kopieringen af den nye fil sker førstkommende nat.
Selvfølgelig er der administration i det, men det er der jo i næsten alt i IT verdenen.

I øvrigt kan jeg se et andet problem i at åbne en db shared - er der ikke nogen ændringer der kræver exclusiv adgang?  I så fald skal du stadig rette i en kopi og kopiere den ud på serveren på et tidspunkt hvor der ikke er nogen 'på'

Der er ikke noget problem i det som sådan - men jeg er nysgerrig efter om det faktisk kan undgås.

trer>As Thomas says, I understand danish 100%, just not so good, and too lazy to write in Danish :o)

Conscerning ADE/ADP files. As far as I know it is only the ADE/ADP file which gets opened exclusivly and further users will only get a read only copy of the AD/ADP file. BUT the data is NOT read only. So you should be able to accpet the message and continue using the application as normal. You can NOT modify the design, but then that isnt necessary!

In my opinion ist is also best to distribute the ADE/ADP to each user although there is more administarion needed. There are applications on th emarket whcih can assist with this. www.fmsinc.com

Hvis HVER bruger SKAL have sin egen .mde/.mdb eller .adp fil, så skal udviklingsdatabasen jo kopieres i tilsvarende antal! :(
(Ikke videre praktisk....)

If we take a closer look at this paragraph>
In practice, when you are running a shared application, you simply provide a copy of the Access project file to each user of the application. In this case, each user has their own copy of forms, reports, data access pages, macros, and modules. But they are in fact sharing one SQL Server database and the tables, views, stored procedures, and database diagrams that reside in that database. Therefore, it's important in a multiuser environment to also provide adequate security on these shared database objects so their integrity is not compromised. Learn about protecting an Access project.

I understand this to say that it is only the ADE/ADP which is read only >"But they are in fact sharing one SQL Server database and the tables, views, stored procedures"
If this wasnt the case then there would be no need to concider what they continue to say>

"Therefore, it's important in a multiuser environment to also provide adequate security on these shared database objects so their integrity is not compromised. Learn about protecting an Access project"

puppetmaster> det er meget praktisk - man kan sidde og udvikle på en database og hvis den skulle blive f..... up, så er skaden ikke sket for alle brugere, men kun i den kopi du sidder og arbejder med. :-)

Okay, Terry - thanks for your answer. I had hoped for a "undisclosed feature" in access allowing adp to be opened in share mode, but it is okay.

Hmmm....man sidder vel ikke og arbejder på en produktionsdatabase, men på en udviklerdb, som så testes af og deployes til brugerne når den virker (ligeså godt som Windows!)

Puppetmaster> Sådan ser verden også ud efter min mening. Uheldigvis bliver man ind i mellem nød til at foretage en nødrettelse direkte i prod - så er det, man er rigtig glad for muligheden for en fuld backup forinden :-)