Moving .xl files between Citrix, Desktop - missing references

Hi,

When you say your user created copies of the workbook, do you mean they simply used the standard Windows (Explorer) facilities to copy a file & rename it, or did they open the MS-Excel file & use the "Save As" menu (or button icon) item?

I am guessing the latter.

In this case, the platform on which the "Save As" is performed will bind to the libraries installed in that environment creating a reference to the local version of any ActiveX control objects, in this case, the "RefEdit" Control.

You could deploy any associated Dynamic Link Library (.DLL) files to the Citrix environment from your desktop installation(s), or you could look at not using that control & coding-up your own using a standard MS-Excel UserForm.

Alternatively, copy the DLL files from the Citrix environment to your desktop environment(s) so that you are developing using the "lowest common denominator" library files across all installations.

If you think copying .DLLs from one environment to another may impact other applications that use the same named library files, then maybe you could just copy the .DLL files that your MS-Excel workbook application relies upon to the folder where the workbook is located.

As long as there are no explicit references to these library files in Declare statements within your Visual Basic for Applications code inside the MS-Excel workbook, then the local folder will be searched prior to the PATH environment variable &/or the Windows, or Windows/System[32] folders to qualify the location of the expected .DLL file when the RefEdit control instance is created in the workbook.

If it helps, you could always set up a temporary folder with all the .DLLs (maybe even on a networked drive available to both Citrix & desktop environments) & amend the users PATH environment variable for the duration of the usage of the workbook to point to the temporary network folder in preference to all other folders already defined in the PATH variable.

This could be done by using a VBScript file that modifies the PATH & then invokes the MS-Excel workbook, or the MS-Excel Visual Basic for Applications code could modify the PATH programmatically during start-up ["Workbook_Open()" ThisWorkbook event code or "Auto_Open()" public subroutine].

As a another option, of course, you could insist that all file manipulation is performed on one platform or another; possibly even disabling the in-workbook menu/button commands by Visual Basic for Applications code if the Citrix environment is detected.

BFN,

fp.