VBA Broken - Unable to Compile

[Chris Bailiss]

Hi all,

I am unable to run any VBA in access XP. I get the compile error of
'Error In Loading DLL'. Behaviour of the wizards is also patchy. I
cannot get past the first screen in most (i.e. the buttons in the
wizard screens are dead). I presume the wizards run VBA underneath.

I have installed the latest service pack, both windows xp and office
xp. It was a clean XP install.

I have tried repairing and reinstalling Access.

When I installed I selected to install everything, and run nothing
from the CD. Curiously, whenever I start Access, I get the
'Installing: Microsoft Access Components' dialog.

I am also unable to run any VBA in Excel XP, nor record any macros.

I have also tried reinstalling the latest version of MDAC (following
suggestions in past posts).

I am pulling my hair out. Has anyone had similar problems?

Would be very grateful for any ideas!

Many thanks,

Chris.

[WindAndWaves]

Try to find out what references you have linked (in module window). Having
the wrong ones listed often leads to this sort of trouble.

There is lots of info on this on the net.
---
Please immediately let us know (by phone or return email) if (a) this email
contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.683 / Virus Database: 445 - Release Date: 12/05/2004

[Chris Bailiss]

References are all fine. I know how to fix that type of problem.

Part of my problem is that I cannot determine which DLL is causing the problem.

Any ideas?

Chris.

[WindAndWaves]

Sorry, I would not know any more.
"Chris Bailiss" <c.*******@btinternet.com> wrote in message
news:82************************@posting.google.com ...

References are all fine. I know how to fix that type of problem.

Part of my problem is that I cannot determine which DLL is causing the problem.
Any ideas?

Chris.

---
Please immediately let us know (by phone or return email) if (a) this email
contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.683 / Virus Database: 445 - Release Date: 12/05/2004

[Larry Daugherty]

Hi Chris,

What kind of error message are you getting? Does it halt on a line of code?
Post back with as much detail as you can and someone can probably help you.

HTH
--
-Larry-
--

"WindAndWaves" <ac****@ngaru.com> wrote in message
news:U8*******************@news.xtra.co.nz...

Sorry, I would not know any more.
"Chris Bailiss" <c.*******@btinternet.com> wrote in message
news:82************************@posting.google.com ...

References are all fine. I know how to fix that type of problem.

Part of my problem is that I cannot determine which DLL is causing the problem.

Any ideas?

Chris.

---
Please immediately let us know (by phone or return email) if (a) this

email contains a virus
(b) you are not the intended recipient
(c) you consider this email to be spam.
We have done our utmost to make sure that
none of the above are applicable. THANK YOU
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.683 / Virus Database: 445 - Release Date: 12/05/2004

[almish]

c.*******@btinternet.com (Chris Bailiss) wrote in message news:<82************************@posting.google.co m>...

References are all fine. I know how to fix that type of problem.

Part of my problem is that I cannot determine which DLL is causing the problem.

Any ideas?

Sure. You can use the MDAC Component Checker to help identify problems
involving those files:

http://www.microsoft.com/downloads/d...displaylang=en

And you can check for dependencies (what DLLs are not loading or are a
wrong version) by using Microsoft's Dependency Walker:

http://support.microsoft.com/default...b;en-us;256872

'------------------------------
' John Mishefske
'------------------------------

[Chris Bailiss]

Whn I try to run the procedure I recieve the error:

The expression On Click you enetered as the event property setting
produced the following error:
Error in loading DLL

* The expression may not result in the name of a macro, the name of a
user defined function, or [Event Procedure].
* There may have been an error evaluating the function, event or
macro.

This error occurs whenever I try to run any code (with the 'On Click'
bit changing as appropriate). The error does not halt on a line of
code. I get the impression it is not getting that far. E.g. if I
select the compile option in the Access VBA editor, I get the same
error and again it does not point to any line of code.

Also, the wizards are broken, i.e. the first screen of each wizard
will appear but the buttons do not do anything in them. Presume the
wizards run VBA underneath.

It also affects the other Office applications, e.g. the VBA editor in
Excel is completely disabled, the menu options are all totally
disabled - I cannot view or add any code to a spreadsheet.

Something is very broken with VBA environment.

Just worth noting, I have done a full install, with nothing running
from the CD.

Any ideas?

Chris.

"Larry Daugherty" <La********************@verizon.net> wrote in message news:<hc*******************@nwrddc03.gnilink.net>. ..

Hi Chris,

What kind of error message are you getting? Does it halt on a line of code?
Post back with as much detail as you can and someone can probably help you.

HTH
--
-Larry-

[Chris Bailiss]

Thanks for that.

MDAC is installed fine.

Used the Dependency Walker:
MSO.DLL seems to be the problem. I have found the file, in:
C:\Program Files\Common Files\Microsoft Shared\Office10
but it doesn't appear to be registered.

Attempts to register or unregister the file using regsvr32 give the error:
"mso.dll was loaded, but the DllResgisterServer entry point was not found.
This file cannot be registered."

Am I registering the file in the wrong way?

Any suggestions?

Thanks again,

Chris

mi****@execpc.com (almish) wrote in message news:<95**************************@posting.google. com>...

c.*******@btinternet.com (Chris Bailiss) wrote in message news:<82************************@posting.google.co m>...

References are all fine. I know how to fix that type of problem.

Part of my problem is that I cannot determine which DLL is causing the problem.

Any ideas?

Sure. You can use the MDAC Component Checker to help identify problems
involving those files:

http://www.microsoft.com/downloads/d...displaylang=en

And you can check for dependencies (what DLLs are not loading or are a
wrong version) by using Microsoft's Dependency Walker:

http://support.microsoft.com/default...b;en-us;256872

'------------------------------
' John Mishefske
'------------------------------

[David W. Fenton]

c.*******@btinternet.com (Chris Bailiss) wrote in
news:82*************************@posting.google.co m:

Something is very broken with VBA environment.

Have you run the REPAIR from the Office Setup program?

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc