Troubleshooting how and why are MVBA files saved when used?

Hi you all,

We have a lot of mvba files ( 36 ) wich are used by our engineers, 12 workstations, al the mvba on a network share. MVBA is used to create drawings, ad cells to drawings, and count cells in drawings and create a csv file with the cell counts, for processing.

All this works, rather well.

Yesterday I discovered, that the dates on the mvba files keep changing by itself, started digging and found out the directory wasn't write protected as it was on the former server we used, so I changed it so that only I can write in the directory, since I think there is nothing in the MVBA files that need saving.

Unfortunatly this causes microstation to complain at startup, because the first thing it seems to want to do when any vba is executed, is save all the vba files. This results in a popup stating it can't save a mvba and if you want to save somewere else. 36 times. These popups have been nown to occur before, but before the whole row popped up just twice, first row of pop ups after te first mvba is called, and the second row by trying to close microstation with the cross at the right top. Then after microstation was restarted everything works.

Now since the rights for the directory are set to read only, there are several, not all, pc's that keep complaining the mvba can't be saved, wile the others  just work

Could be a problem caused by the last or last before that update of Microstation ( were running V8i select 08.11.09.829 now) because all the mvba files used to be on a totally write protected server. Or perhaps have something to do with the way Microstation is installed, since most of the pc here are replaced ( there are new pc's with the problem, and also new pc's without the problem.)

So now the question is, is this a setting I can turn of, or is this caused by the MVBA? And if it is the vba, how do I troubleshoot this?

But given the fact all the pc's work with the same mvba, from the same directory, and not all the pc's have the problem I think it must be a setting somewhere.

 Any Idea's are greatly appreciated

Parents
  • Hi ,

    Can you confirm if you may be seeing the Microsoft Last Accessed Time vs. Last Modified Time stamp changed?

    Using Microsoft Process monitor against MicroStation CONNECT Update 13.1 and having several .mvba projects in my autoload, I do not see any Write operations against the .mvba file extensions using this tool when simply loading MicroStation, entering a design file, loading the VBA project manager, then opening the Microsoft VBA editor (no changes to any items in any projects).

    If you are seeing changes to the Last Modified time stamp, can you zip and attach a list of your MicroStation configuration variables?
    MicroStation key-in: SHOW CONFIGURATION.

    Thank you,
    Bob



Reply
  • Hi ,

    Can you confirm if you may be seeing the Microsoft Last Accessed Time vs. Last Modified Time stamp changed?

    Using Microsoft Process monitor against MicroStation CONNECT Update 13.1 and having several .mvba projects in my autoload, I do not see any Write operations against the .mvba file extensions using this tool when simply loading MicroStation, entering a design file, loading the VBA project manager, then opening the Microsoft VBA editor (no changes to any items in any projects).

    If you are seeing changes to the Last Modified time stamp, can you zip and attach a list of your MicroStation configuration variables?
    MicroStation key-in: SHOW CONFIGURATION.

    Thank you,
    Bob



Children