VBA program always prompting to save .DVB on close

[amy.143074]

I have a VBA program that, as far as I can tell, has not given us this problem before, but now, with certain users, it always seems to prompt the user to save the .DVB file when AutoCAD is closed. The macro is loaded and runs without any known problems, but no changes are actually made to the VBA. But every time AutoCAD is closed, the prompt is given:

"Do you want to save the changes you made to the VBA project "path...\Program.dvb"? (Yes) (Yes to All) (No) (Cancel)"

We're running AutoCAD 2008, SP1. Can't recall if this problem was occurring before we upgraded from 2006, but it's possible.

What settings, either in AutoCAD or in the VBA code might be causing this to happen? It's causing confusion among our users, and making it hard for us to debug issues when everybody has a different saved timestamp on their programming.

Thanks!

[ed.w.cler]

I had a similar problem in Inventor. Since I am the only one that does any programming, I set the read/write permissions in Windows such that I was the only one that had write access to the *.idv (the inventor *.dvb equivalent). This resolved the issue for me, and also helps keep the macro file from being inadvertently edited.

[Coolmo]

I just did a quick test to see what would happen if I opened the Visual Basic Editor and double clicked on one of the userforms in the project. Even without changing anything in the project but just clicking the userform from the Project Explorer, it prompts me to save the project when quiting AutoCAD. Are any of your people getting into the DVBs and clicking around but not changing anything?

[amy.143074]

ed.w.cler: Unfortunately, that's not an option for us -- we have several people on our team who are in and out of the programs on a regular basis. Thanks for the tip, though, and I will keep it in mind.

Coolmo, I don't think most of these users would know how to click around in the code. And on these particular machines, I was able to replicate the error simply by loading the macro and unloading it, without touching the editor. Most of our programs don't do this -- just one, and I don't think everyone is having the problem (if so, they haven't all reported it).

Most of our macros are called from other macros... we frequently load and unload our DVB files from within other VBA code, and this one is no exception...

[rkmcswain]

For those people who DO get prompted, do they have proper rights to save the file in place? Are they saving it?

[Ed Jobe]

Most of our macros are called from other macros... we frequently load and unload our DVB files from within other VBA code, and this one is no exception...

How? Does it involve using vbe? Are you setting references? Are you changing the code programatically?

[amy.143074]

rkmcswain: They all have rights to save the VBA to the place they run it from. I have told them to click "No," I think occasionally they're clicking "Yes." Regardless of which selection they make, they get prompted again either way.

In one case, when the prompt came up, I made a copy of the existing file before answering the prompt, and then selected "yes" and grabbed a copy of the resulting file (it does get saved, judging by the timestamp). Comparing the two, I couldn't notice any code differences, but the file size on the second file (after selecting "yes" to the prompt) is considerably larger in file size -- almost double.

Ed Jobe: I use RunMacro (path & "Program.dvb!runThisMacro") and UnloadDVB(path & "Program.dvb") functions to run this vba. We do not programmatically modify the code, or at least not that I'm aware of. Didn't know that was possible.

If I get a chance this afternoon, I'm going to try and find a way to more thoroughly compare the code between the two programs and try to spot any subtle differences. I don't expect to find any as far as code goes, but I'll update if I do.

[Ed Jobe]

Use WinDiff to compare them. Save the context of each to a txt file first. Windiff can't read the compiled dvb.

[Coolmo]

BTW, I've noticed that if I save a DVB file from my computer at work and then take it home to work on it from my laptop, the file size is wildly different even without changes to the code. I simply get into the code, don't change anything but still hit SAVE. When I take the DVB file back to work and copy it back to my work computer, it asks me to overwrite the file and shows different file sizes... sometimes almost double the original file size. Weird. I just assumed the different computers were saving it a different way.

[rkmcswain]

BTW, I've noticed that if I save a DVB file from my computer at work and then take it home to work on it from my laptop, the file size is wildly different even without changes to the code. I simply get into the code, don't change anything but still hit SAVE. When I take the DVB file back to work and copy it back to my work computer, it asks me to overwrite the file and shows different file sizes... sometimes almost double the original file size. Weird. I just assumed the different computers were saving it a different way.

SAVE and SAVEAS are different in the VBA editor.
SAVEAS also does sort of a "PURGE", resulting in a much smaller file usually.