Citrix Deployment - Must have Bat File so each users has copy of Front-End (1 Viewer)

Rx_

Nothing In Moderation
Local time
Today, 10:26
Joined
Oct 22, 2009
Messages
2,803
The echo is optional, used to explain what is happening. xx is the actual version of Access on the Citrix Server. The Citrix Admin will need to use the actual location of MSACCESS.EXE.

Code:
@echo Please wait while the latest version of the Front-End user database you requested is updated to your own personal folder.
@echo off
MD "X:\Database\"
xcopy /Q /Y R:\Front-End\Current\MyLatestVersion.mde "X:\Database\*.*"

TYPE NUL | choice /c:delay /td,5 >NUL
Start /max "E:\Microsoft Office\OFFICExx\MSACCESS.EXE" "X:\Database\MyLatestVersion.mde" 
exit

Da' Rules - Each user gets a folder - the folder has a copy of the latest Front-End copied in that folder. The Front-End should use Linked Tables to a common Access DB (back-end) or Linked Tables to something like SQL Server.

New Release: R:\Front-End\Current\MyLatestVersion.mde
Navigate to this network folder, delete the last front-end copy and replace it with the new release. The name: MyLatestVersion must be the same since it is called on to be copied to each user's individual folder.

When a user is in a Citrix session, the individual user folder will display the locking file, showing it is active. Once in a great while, a session is terminated.
If the locking file remains, it may be necessary to manually delete it.

Coding: if you have many concurrent users, it is highly advisable to keep transactions very short. Avoid locking a file while the user completes three fields. Learn more about a recordset becoming "dirty". Trap errors to exit gracefully. These are things that any multiuser front-end should have. Bottom-line - code may work perfect for one user, fail when dozens or hundreds of users are active.

Special Thanks to Bob Larson who helped me with this several years ago.
 

Users who are viewing this thread

Top Bottom