Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

USES ComObj or Excelxx causes C0000005 Access Violation

Status
Not open for further replies.

6volt

Programmer
Jun 4, 2003
74
US
Delphi 7.

If I uncheck Access Violation in Debugger Options, I don't get the error.

Checked this issue on other machines in office and they DO NOT behave this way.

The code that does this is a new Project1 where I merely add ComObj or Excelxx to the USES, then hit the green triangle run button.

I have replaced ComObj and Excel97 and have done a repair install of Delphi 7 and it still does it.

Any thoughts?

Could something be damaged in the WindowsXP Pro OS on this machine?

Thanks in advance,
Tom
 
seems to me you have a corrupt OLEAUT32.DLL. Maybe repairing your windows system may help. Dou you have problems when copying excel objects to word (for example)?

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
whosrdaddy:

I just tried playing around with an XL chart that I dragged into a Word doc. I was able to OPEN that object from Word and then edit the values in XL.

I did this on 2 PC's, one "good" one and the one with the problem.

I couldn't see any different behavior between the two.

Still, I feel that the problem is something as you suggest.

I'm going to check out that DLL and see if I can detect a difference between PCs - maybe a binary compare...
 
do you have the same issue when you include the activeX unit? (only that unit)

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
lookaing at the code in activeX unit and I see it references those dll's:

ole32 = 'ole32.dll';
oleaut32 = 'oleaut32.dll';
olepro32 = 'olepro32.dll';


so one of them must be your problem...

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
I tried the USES activex and it is OK - no problems.

Each of the following produce the C0000005:

ComObj, Excel97, Excel2000, ExcelXP
 
Did some surveying to find that EVERY file in the Ocx\Servers directory produced the same identical access violation:

ox7c83227d: Read of address 0x0000c038

the dump show a line of code just after

kernel32:IsBadStringPtrA

Some files in the lib\ directory were bad: DBOleCtl

and some were good: activex, comapp, comctrls

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top