View Single Post
  #2   Report Post  
Posted to microsoft.public.excel.programming
Norman Jones Norman Jones is offline
external usenet poster
 
Posts: 5,302
Default Missing library in Object Browser

Hi Jo,

With the workbook in question active, run the problematic code

When the code errors, go to the VBE and select the project in the Project
Explorer Window

Hit the reset button and look at the Tools | References list

Look for any references marked as "MISSING".

Either uncheck the reference or, if the reference is needed, try the browse
button to locate the library,


---
Regards,
Norman



"Jo Winchester" wrote in message
...
I am looking at an issue with an Excel spreadsheet. The spreadsheet
contains
4 forms, two of which are throwing up errors.

The code that is causing the issues is as follows:

Private Sub UserForm_Initialize()
Me.questdate.Value = Date
End Sub

Private Sub UserForm_Initialize()
Me.Startdate.Value = Date
Me.Enddate.Value = Date
End Sub

The problem is intermittent. We work in a published Citrix Environment,
with Windows 2000 servers hosting a published desktop. We are running
Excel
2000 on all servers.

On some servers, the spreadsheet works as expected. On others it fails.

On the servers that work, it is possible to open Object Browser, search
for
questdate, startdate or enddate, and it returns:
Library: f3dynamic
Class: Userform
Member: <searchstring

On the servers that the code doesn't work on, no results are returned.
I have search on a working server for files called f3dynamic, but no
results
are returned.

All access to our servers by users is via ICA connections. Tests have
shown
the following results:
Launch ICA connection with standard user account - Spreadsheet errors
Launch ICA connection with a high priv (domain admin) account -
Spreadsheet
errors
Launch RDP connection with a high priv (domain admin) account -
Spreadsheet
works as expected, f3dynamic library can be viewed, and spreadsheet is
then
OK for all other users.

I have tried filemon and regmon monitoring, without much success.

Can anyone suggest any further next steps to resolve this issue?