Results 1 to 12 of 12
  1. #1
    JustCallMeAl
    Guest

    Emergency Help! VBE.DLL crash

    We changed our server yesterday, giving it another name. I did go through the macros and make sure there was no UNC referencing.

    Today, many people are crashing with VBE.DLL being the "culprit."

    I have NO idea what is the reason. I checked MS Knowledgebase and couldn't find anything that helped.

    Your great assistance is appreciated.

  2. #2
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    Al,

    Remove the reference "Visual Basic Application Extensions" in your App, save the app and let 'me have at it again.

    You could also restore (copy) the VBE.DLL file to the LAN location is was before the upgrade, but better practice says that reference is only necessary for developing. It's a waste of resources (IMHO) to distribute production code with that reference.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  3. #3
    JustCallMeAl
    Guest

    Re: Emergency Help! VBE.DLL crash

    When you say remove the reference... is this on each machine? In my programming environment? I am not quite clear where this is to be done.

    Thanks

  4. #4
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    On your machine only. Here's the rub:

    You've got (I'm almost certain this is the case, but there may be some other source of the problem) -- you've got a reference to the VBIDE objects in your code. If you remove this: (in the IDE, click Tools>References -- you know this, I know) and uncheck that reference, then save the code, you'll have removed the reference in the code. Now the app will no longer look for VBE.dll. Let me know.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  5. #5
    JustCallMeAl
    Guest

    Re: Emergency Help! VBE.DLL crash

    Let me just repeat what I understand at this point.

    It is the individual documents with a VBIDE reference that is causing the problem. Therefore, by opening that document, removing the reference, saving the document, the problem should be solved.

    Is that a correct summarization?

    Thanks

  6. #6
    JustCallMeAl
    Guest

    Re: Emergency Help! VBE.DLL crash

    *$%&$(*$* Now I can't even go into the IDE at my computer!

  7. #7
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    Sorry for not being clearer. I'm looking at your problem from my point of view: I code to one main app (and only that app would ever contain a reference to VBIDE). Any other template or global (and there are lots of them) are about as naked as they can get -- any code in them is there cause I'm too lazy to "code it up right" or there is just no other way to do it.

    Now, in your case it sounds like you've got a template (or templates) from which users are trying to create new docs, and these templates have a reference to VBIDE. You'll have to remove the reference it each template.

    But maybe in this case (since there may be *lots* of said templates) you could just copy the VBE.dll file back to the LAN folder it was it before the upgrade. The only question is "do you know where that is?"
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  8. #8
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    Could it be that Office (btw, what version?) was installed to the LAN and not to your PC?
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  9. #9
    JustCallMeAl
    Guest

    Re: Emergency Help! VBE.DLL crash

    Thanks for your great help, Kevan.

    It appears that the cause was..... ::drum roll please:: ....missing file Share attributes being set! In other words, when all of our templates were copied from the old server to the new one, they kept their read-only attribute, but they lost their Share attribute.

    At this stage, this is still an hypothesis; however, we have some pretty strong circumstantial evidence pointing to that fact, including that when we had everyone change their Workgroup Templates path back to the old server there was no problems. But, we will be doing more testing the rest of the week.

    The testing consists of setting the Share attribute, of which we have four templates that we cannot set the Share attribute yet, i.e., people are in them, so I will reset them tomorrow morning first thing. Then I will be moving about 1/4 of the users to the new server each day, which will this time occur programmatically. That way, if there is a problem, hopefully it won't shutting down the entire office again.

    Again, thanks for your help.

  10. #10
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    ...de Nada,

    You really oughta remove the reference too. Tell me you're going to remove the reference. You're going to remove the reference, right?

    Btw, Al, I'm Kevin, not Kevan. There is a Kevan posting too from time to time.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

  11. #11
    JustCallMeAl
    Guest

    Re: Emergency Help! VBE.DLL crash

    re your name. I've seen it both ways, but.....sorry.

    If the hypothesis holds true, then we can do something about the references. I have found since writing this morning that there was a reason why that reference existed. However, last July when the programmer left, the reason left too. [img]/forums/images/smilies/smile.gif[/img]

  12. #12
    Gold Lounger
    Join Date
    Dec 2000
    Location
    Hollywood (sorta), California, USA
    Posts
    2,759
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Emergency Help! VBE.DLL crash

    Al,

    Unless I'm missing something in my understanding, the reference to VBIDE is only necessary if you *need* the object model class names for everything. Gotta go for now, but tomorrow I'll post some simple code that uses compiler directives to help with using the reference while development and production code.

    Maybe somebody'll beat me to it.
    Kevin <IMG SRC=http://www.wopr.com/w3tuserpics/Kevin_sig.gif alt="Keep the change, ya filthy animal...">
    <img src=/w3timages/blackline.gif width=33% height=2><img src=/w3timages/redline.gif width=33% height=2><img src=/w3timages/blackline.gif width=33% height=2>

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •