M
Max Moor
Hi All,
I have two database applications. Both are in Access 2002. One has
been around a few years. I decompile and recompile before each release
without issue.
The second application is relatively new, with most of its guts
imported from the older app. Everything seems okay with the new app, in that
it compiles and runs and such.
When I try to use the /decompile switch on it, I get a message that
"Microsoft Access has experienced a problem and needs to close. We're not
sorry enough for the inconvenience to give you any real information."
I might be paraphrasing a bit there at the end.
I've done a compact and repair, and have even opened a new database,
and imported everything into it. It still does it. Should I be concerned
that the database can't decompile without exploding, when it seems okay
otherwise?
Thoughts?
- Max
I have two database applications. Both are in Access 2002. One has
been around a few years. I decompile and recompile before each release
without issue.
The second application is relatively new, with most of its guts
imported from the older app. Everything seems okay with the new app, in that
it compiles and runs and such.
When I try to use the /decompile switch on it, I get a message that
"Microsoft Access has experienced a problem and needs to close. We're not
sorry enough for the inconvenience to give you any real information."
I might be paraphrasing a bit there at the end.
I've done a compact and repair, and have even opened a new database,
and imported everything into it. It still does it. Should I be concerned
that the database can't decompile without exploding, when it seems okay
otherwise?
Thoughts?
- Max