[V8i SS3 VBA WIN10 64]

Hi Everoyone

Recently I was obliged to move to brand new machine (Dell 5530/Quadro320/I9..Windows10 v1809).

For me and company we have lots of VBA extensions (some pretty much developed and complicated).

I've tried to run one of it on my brand new PC and whole ustation crashed (without error code).

To be more compatible with whole company, we are using ustation V8 ss3/ss4 + Office 2013 (same VBA code is used even by V8 2004)

But right now I cannot start none of VBA code.

At the end of the day, I tried to:

1) record macro (silly) - SUCCESS - it was working

2) start very simple 'msgbox "hello world"' in VBA module - SUCCESS - it was working

3) add FORM, place a button and display 'msgbox "hello world"'  - NOT SUCCEED - it has crashed with error "Run-time Error -2147417848 (80010108)"

So - I'm lost. 

in C:\Program Files (x86)\Common Files\microsoft shared\VBA, there are both VBA6 and VBA7.1 folders. 

Can someone give me advice - what is the reason, and what is more important, how to solve it?

Thanks in advance.

  • Hi,

    My guess is something is wrong with references.

    Error when using Form points to references.

    Open VBA-Project- Tools-References and check if any is missing.

    regards

    Nenad

  • add FORM, place a button and display 'msgbox "hello world"'  - NOT SUCCEED

    That suggests that MicroStation VBA MSForms is unavailable, or that a different version of MSForms has been installed.  What happens when you compile (menu Debug|Compile) that module that contains a UserForm?

    You may be able to repair the VBA installation.  Search these forums for similar questions: I don't recall whether the repair pack is available from Bentley Systems or Microsoft.

     
    Regards, Jon Summers
    LA Solutions

  • Hi,

    I'm just going by memory, but I think that the order in which things are installed can make a difference.  I usually install MS Office fires, then Microstation afterward.  Have you tried reinstalling Microstation?

    --Robert

  • Hi again (sorry for being late - I was on a business trip).

    Thanks for all replies. Iv checked them, and:

    1) Nenad: - I've checked and all ref. are found. (but dont know if proper versions of them)

    2) Jon - Compile does nothing - no responses from machine; 

    I will try to find REPAIR PACK for VBA, and will share results

    3) Robert - yes, I was trying reinstalling Office / Ustation - no results...

    OK, I've tested lots of combinations:

    - uninstalling / reinstaling MS Office / Ustation - no results

    - copying "old" files from other PC' (W7) - no results

    Tricky thing is, that FORM can be loaded and works as long as there is none of commands connected to buttons etc. After pushing button - there is message: "Connection to type library or object library for remote process has been lost." Run-time Error -2147417848 (80010108).

    I believe, that Ustatin is able to start form for the first time after ustation startup, by command UserForm.Show, but after crash - it could not be loaded again. An what is more - VBA REFERENCE shows none of missing library

    Is it possible, that W10 defence stops the VBA macro from running? Is it possible to enable something like "trusted" MVBA?