"Save changes to xxx.dvb?" NO! I didn't make any!!

I've seen a few posts about this in the past, however, there weren't any
answers posted.
So I figured I'd give it a shot...

I've got a DVB that I've been working on for quite some time now, and all of
a sudden, whenever I load --> run --> unload the program, I will be prompted
to save changes. I haven't made any to the code so why does this show up??

I am completely and utterly perplexed!
If anyone can offer any insight as to what might be going on or what I can
look for, I'd appreciate it.

Thanks in advance!

 

This is a complete WAG coming from a relative novice: Do you have some
custom code running within the IDE? (I've never done such a thing, but from
what I read, it is possible.............I'm thinking some code is running
that is actually changing the code.)

 

Not the case here, but thanks for the input.

 

I don't know about the issue you mention, but there are problems with acad's
vba system.
(imho)

You are aware of the dvb bloat bug? Periodically do a saveas from vbaman to
clear the excess, and see google for discussions of this.
Also I've had many dvb's become completely unreadable just out of a clear
blue(apparently) - thus losing many hours of work - therefore I always
export all modules,classes,and forms to their own files for safe keeping -
and reexport with every edit to keep them up to date.
I've never had problems with .bas, .cls, or .frm files going bad, but .dvb's
definitely.
again a google search will turn up an autosave module from (ed jobe or kevin
terry???) to automatically save the modules for you.
maybe search on "vbe"

good luck
I have a hunch the saveas may help but its just a wag.
Mark

 

I've heard about the "bloat bug".
It doesn't seem to be an issue here. The file size seems appropriate for
the amount of code and forms in the project.

Just for the halibut, I opened the project, then closed all of the code
windows, then saved the project and then unloaded it.
The next time I ran it then unloaded it, it worked fine.

I can't imagine that having a code window open would trigger something like
this, but that appears to be the case. Go figure!

 

Sounds like you were opening a dvb that hadn't been compiled. Look back at
the aforementioned threads and see what I said about compiling. If you
opened a file that hadn't been compiled, when the user runs it, it would
have to compile before the requested function can execute, thus altering the
file and prompting the save. FWIW, I've never had any dvb's corrupt since
began the practice of manually running Debug>Compile after making changes.
It saves the hassle of exporting/importing. Also, it prevents the true
problem of corrupt dvb's, compile errors. This step catches those before you
close the dvb and alerts you to fix them. Then you can safely close the dvb
and be assured you will be able to reopen it. Here's another tip I
discovered about compiling - the project browser display arrangement is
saved only when you compile. IOW, when you reopen the vbaide the first time
after acad is opened, the tree structure is restored from those settings. If
you want to always come back to a collapsed tree structure, collapse the
tree and then compile.

BTW, acad is not the only product that can have this problem. Any file
format that saves vba code with it, pseudo code and compiled code, can do
this. I've had Access mdb's corrupt on me too. Only Access has an
undocumented startup switch, "/decompile", that strips the compiled code out
of the dvb. Then it will open again, you fix the compile error and resave.
There are some things to beware of though. Before you try this, you should
read this: http://www.trigeminal.com/usenet/usenet004.asp

 

Thanks for the feedback.
FWIW, I had been compiling the project after every change (as far as I know
anyways), then it seemed to just come from out of nowhere.
So then I closed all of the windows, then made sure I compiled it, and the
problem has since gone away.

I don't know... maybe I didn't compile it, but I could have sworn that I
had.
Oh well, problem solved (for now).

Thanks again!

 

You must be gettin' old, like the rest of us.

 

I'm gonna hold onto my 20's for as long as I can!

 

Just for the halibut, I opened the project, then closed all of the code

[pre]
halibut - A large fish with a flattened body adapted for life on the seafloor.
---- Source: Google's "define halibut"
[/pre]
Wild guess: This is rhyming slang for "hell of it"?

Regards

Wayne Ivory
IT Analyst Programmer
Wespine Industries Pty Ltd