Smitty
Legend
- Joined
- May 15, 2003
- Messages
- 29,536
I just built a new tower system to replace my older laptop (it's a real screamer BTW, so if anyone wants specs just PM me).
I'm now Running 64-Bit Windows & Office 2010, as well as 32-Bit Vista & Office 2003 in a VMWare Virtual Machine to support older apps.
I was working on a 2003 db in the Virtual Machine and shut it down (for some odd reason VMWare needs to be shut down every few hours or it just gets progressively slower), then opened it in 2010 to check something. When I reopened it in 2003 I got a "VBA Project Corrupted" error message that required a hard shut down to exit. I then got the same error in 2010.
I know that the 64-Bit versions require some additional VBA security protocols/checks, but has anyone else experienced the corruption error?
Fortunately I had a backup and lost very little work, but it's still a PITA, so if there's a way to program in a prevention I'm all over it.
Thanks,
I'm now Running 64-Bit Windows & Office 2010, as well as 32-Bit Vista & Office 2003 in a VMWare Virtual Machine to support older apps.
I was working on a 2003 db in the Virtual Machine and shut it down (for some odd reason VMWare needs to be shut down every few hours or it just gets progressively slower), then opened it in 2010 to check something. When I reopened it in 2003 I got a "VBA Project Corrupted" error message that required a hard shut down to exit. I then got the same error in 2010.
I know that the 64-Bit versions require some additional VBA security protocols/checks, but has anyone else experienced the corruption error?
Fortunately I had a backup and lost very little work, but it's still a PITA, so if there's a way to program in a prevention I'm all over it.
Thanks,