I recently had to identify the fact that the CITRIX server was maxing the CPU and thus the database application I designed was miserably slow.
Insufficient Server capacity – Since the CITRIX server is an application server, it is crucial to ensure sufficient RAM, CPU power,….Where I have seen issue occur… Well, there can be a number of issues, but 2 specific issues seem to keep coming up recently.
#ACCESS CITRIX ON MAC KU MED FULL VERSION#
Of course, as with any installation, a reliable backup system must be put in place and validated on a regular basis.Īs a developer, I always need to be given an administrative console with the full version of Access installed so I can perform tests, and more importantly compile my application locally to ensure proper compatibility. By doing so, the database runs completely on the CITRIX server and there is no network impact, and the database also doesn’t take up valuable network bandwidth uselessly. Typically, in an effort to minimize the impact of internal networks…, I like to try and have the back-end installed directly on the CITRIX server itself. Like with every MS Access database, to deploy it, you must first split the database into 2 components: front-end and back-end and then issue a copy of the front-end to each of your users. That said, like everything in life, there are both pros and cons to such a deployment of your database.
We see many postings on various forums from people wanting to know more about running an Access database via CITRIX.įirstly, since Access is not recommended to be used over a wireless connection, nor a WAN, CITRIX is a very interesting solution to giving access to such databases.
This is a preliminary posting on the subject, one that I hope to add to over time.