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
Hi Leo,
I have multiple mvba files that keep their last modified dates the same.
I do have a situation where the mvba file may be self-modifying. (They update the path of referenced mvba's to the current project path.) Do you have a situation like that where the mvba is modifying itself?
--Robert
Hi Robert,
Thanks for the input, but there is nothing in the vba that saves VBA, or should save VBA. They are all static.
But it looks like Bob saved the day, because the setting he suggested seems to have fixed the problem, although I must say, reading back, Jon Summers has also pointed in that direction, but I didn't understand it at the time how to put the setting in Microstation, so again I learned something.
Robert Hook said:MS_VBA_OPEN_IN_MEMORY=READONLY
I put this on three PC's and it looks like it works. There is a fourth PC with the problem were it doesn't seem to work, but perhaps a restart will fix that.
Still I think it's strange the PC's that didn't have the problem also don't need the "MS_VBA_OPEN_IN_MEMORY=READONLY" setting??
I'll do some more testing next week and report back here.
Thanks, Leo.
Hi Leo van der Hoeven,
Let's give credit where credit is due. I completely agree with Jon Summers' recommendation including the part of setting permissions on the network share level (my preference) so MicroStation w/o configuration will do the right thing from the start.
If you find Jon's advice is sound in your testing, please click: More > Verify Answer; on his Reply.
Good luck and thank you,Bob