Connect Update 12 - VBA Projects not saving

It appears that if you create a new project then it saves fine, but if you try to work on the same project after you load it, then it becomes read only, although the file itself is not read only. Trying to saveas at this point will crash your microstation and you will loose all your work. Has this been reported?

Version 10.12.00.40

Parents
  • Hello Viktor,

    together with "What does this mean - "??È" when referring to ModelName?" I would guess you might have a corrupted installation/environment. Did you have the same effect on an other computer, best if this computer is not part of your normal environment (AD, etc.?)

    Mit freundlichen Grüßen / Best regards
    Volker Hüfner

    |  AB_DATE Engineering  Software   |  ab-date.de  |

  • Just verified that this behavior is consistent on several machines. To duplicate, do the following:

    1. Create new VBA Project, at this point, the save is available and many any changes will enable the save button. Looking at the titlebar of IDE you can see that there's no "Read Only" next to filename.

    2. Close microstation

    3. Open microstation and load that same project. At this time the project is read only and you will not be able to save. You can saveas, but this only seems to work sometimes, it crashes frequently and also just doesn't save. I don't know how many times I had to export out the modules to recreate the project.

    Thanks.

  • Hi ,

    In the earliest release of MicroStation V8 sharing MicroStation VBA project (.mvba) files over a network with 20+ simultaneous users; our users would encounter Microsoft's builtin client access licensing (CAL) restrictions.

    In the process of addressing this for our users our developers found the Microsoft VBA (APC APIs) interface provided an option to open a VBA project (All or, partially - readonly, or none/default) in memory vs needing to maintain a read and/or read/write lock on the physical file. We were able to provide the MS_VBA_OPEN_IN_MEMORY configuration variable to permit such tuning.

    Given what I see, can you try adding and setting this variable to either: ALL or READONLY and see if that permits the load of your shared VBA?

    Also, if possible it is often best for the developer to modify a local .mvba file (read/write and having full local admin permissions), fully test, then update/deploy the .mvba file to its preferred/final location.

    Also, FWIW. the Microsoft VBA Editor Save (icon) is not required/used since we automatically write and flush any changes needed to the VBA project so no changes are ever lost.

    HTH,
    Bob



  • Well, it was set to ALL already, so I changed it to READONLY just to see the difference and that fixed it... why is readonly setting making it writable? interesting...

    Thanks.

Reply Children
No Data