Missing references in mde frontend

[easyit]

Hi,

I know this has been covered to some extend in other threads, but I cannot find the clues that I need to solve my problem.
I have a application with a front end for which I recently rolled out a new version. On some computers the mde (access run-time is installed for each client) there are 'some' missing references:

C:/winnt/system32/scrunn.dll
c:/winnt/system32/wshom.ocx
c:/programfiles/normale bestanden/microsoft shared/vba/vbag/vbegext.ocb
c:/progra"1/micros"/office/ms04tlg.olb
c:/programfiles/microsoft office/office/excel 9.0 lb
c:/program files/normalebestanden/microsoft shared/dao/dao360.dll
C:/winnt/system32/stdde2.hb
c:/programfiles/microsoftoffice/office/msaccg.olb
c:/programfiles/normalebestanden/microsoft shared/vba/vbag.bll

...where 'some'is ALL my references.

The client machines are running NT4, I develop on a win2000 machine. I have rolled out many versions this way, never a problem. I'm looking fort clues to find out what has changed recently, why are these machines having problems finding the references? What could I have changed in the original app that causes this behaviour?

EasyIT

 

[JerryKlmns]

Add References using VBA thread705-903662

 

[easyit]

Jerry,

Thanks, but I'd read the thread (and the source at Microsoft:

http://support.microsoft.com/kb/q194374/)

and it says that this is not possible for mde file. Also, since apparently I've changed something without knowing it, I'm hoping to find out what& how it has changed.

EasyIT

 

[easyit]

Hi,

I may have solved my problem, for those that are interested. it seems that my front-end is corrupt. Within my corporate environment(NT/2000 office2000) it didn’t show, but at home I use XP and office 2003. Access2003 immediately warned me about corruption in VBA when I opened my fe. I'm replacing the corrupt file with a new one, see how things work out.

EasyIT