This week's book giveaway is in the OCAJP 8 forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide and have Edward Finegan & Robert Liguori on-line! See this thread for details.
Hi. I am using Visual Age 3.5 and I keep getting an error message when trying to open it: IDE.EXE - Application Error The instruction at "0x045b2080" referenced memory at "0x045b2080. The memory could not be "read". I did figure out that it has something to do with the ide.icx (workspace file). If I replace it with a backup copy that I have, I can get into VAJ, but this is a pain seeing as how I have to add everything back to my workspace from the repository. But, as soon as I exit Visual Age and try to get back into it, I get the error message again. I would be forever grateful is someone could give me any sort of clue on how to fix this problem. (I have tried reinstalling, still get the message.) I am running Windows 2K. Thanks in advance!
We have applied Patch2 and still get the error message. Any other suggestions? Just a note: Tried using another machine and totally recreating my application. The minute I got out of it and back into it, the error message now appears on the other machine. Could it possibly be something in the application causing this?? Thanks!
I'm having the same issue. Any answers would be greatly appreciated! I got this error just after my test application ran into a deadlock on a DELETE statement issued to a remote DB2 database. It was impossible to kill the application within visualAge - even after recycling the remote server and client connection . So I exited out of VisualAge, which I was able to do gracefully, and re-booted my machine. I haven't been able to get into VisualAge since. [ December 11, 2002: Message edited by: D Clough ]
You have a dead workspace file. This happens fairly commonly in VAJ. This is why you should keep backups of your workspace often. There is no solution other than to go back to the default ide.icx and rebuild it from the repository -- at least everything is in the repository and you have not lost any code -- just some time. Kyle