Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Do you actually <strong>need</strong> to find out if there is a newer version? </p> <p>We have a similar setup as well, and we just copy the frontend and all related files <strong>every time</strong> someone starts the application. </p> <p>Our users don't start Access or the frontend itself. They actually start a batch file which looks something like this:</p> <pre><code>@echo off xcopy x:\soft\frontend.mde c:\app\ /Y c:\app\frontend.mde </code></pre> <p>When we started writing our app, we thought about auto-updating as well and decided that just copying everything everytime is enough. </p> <p>We have enough bandwidth, so the copying doesn't create any performance problems (with about 200 users). </p> <p>Plus, it makes some things easier for me as a developer when I can be sure that each time the application is started, the frontend is overwritten anyway.<br> I don't have to care about auto-compacting the frontend when it's closed (and users complaining that closing the app takes too long...), and I don't have to deal with corrupted frontends after crashes.</p> <hr> <p><strong>@Lumis - concerning the custom icon:</strong><br> Ok, maybe I should have made this more clear. There is only <strong>one</strong> batch file, and it's in the same network folder as the frontend.<br> The users just have links on their desktops which all point to the same batch file in the network folder.<br> This means that:</p> <ol> <li>future changes to the batch file are easy, because it's only one single file in one central place</li> <li>we <strong>can</strong> change the icon, because what the user sees is a normal Windows link</li> </ol> <p><em>(By the way, we did <strong>not</strong> change the icon. Our app is for internal use only, and I'm working in a manufacturing company, which means that all but very few users are absolutely non-technical and couldn't care less about the icon, as long as it's the same on all machines and they know how it looks like so they can find it quickly on their desktop...)</em></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload