BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Re: ADOCommand Text Editor Access Violation

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (ADO)
View previous topic :: View next topic  
Author Message
Jim Fleming
Guest





PostPosted: Thu Mar 04, 2004 6:51 pm    Post subject: Re: ADOCommand Text Editor Access Violation Reply with quote



Following my inconclusive post on 26 Feb last, we are surprised that no one else has this problem.
Anyone got any comments on this, or has seen the same problem and found a way around it ????

For what its worth, here is a new twist on the same theme:

1. Drop a TADOCommand on your form.
2. Enter 'SELECT * FROM <your table>' into the Command Text property using the property editor.
3. Now create the connection string using Oracle OLE DB Provider. All OK !!!!
4. Enter the Command Text editor, change nothing and exit again. Voila ! Access Violation, but in
"msdart" this time, not in msado15.dll as before.

If you create the connection at design time and add the CommandText property at run time, all goes
OK.

We were trying the above variants of the original problem reported in order to try to debug through
ADODB to see if we could narrow down the problem, as it occurs in the originally reported problem in
the GetCount procedure of the Classes unit when it is called from the AssignCommandText method of
the ADODB module. The call sequence, starting from the point where you click the editor button is:
SetPropValue in Ideinsplistbox.pas unit.
SetStrValue
SetStrProp
SetWideStrProp
AssignCommandText
GetCount

Oracle said to try reproduce the problem with Visual Basic. No luck -- it worked correctly. However,
that environment is sufficiently different to not give me any assurance that we are creating the
same conditions.

If anyone from TeamB would like to have a look at this to try to either determine the problem is
Borland's or Microsoft, not having Oracle available for testing is a problem that can be easily
solved. We want to get this sorted out, as it is not funny having to create Stored Procedures for
even the simplest database operations.

The post to Quality Central has produced no visible reaction at all, leading me to believe that
either all Borland developers are extremely busy or don't ever bother to look at postings there.

Jim Fleming


Back to top
Jim Fleming
Guest





PostPosted: Fri Mar 05, 2004 11:47 am    Post subject: Re: ADOCommand Text Editor Access Violation Reply with quote



Oracle Support has now replied that the problem seems to be in the Borland code calling the
Microsoft ADO API routines -- not in the Provider, as the call stack does not get that far before
raising the Access Violation. But who knows !!!

I'd be a lot happier if someone (maybe Brian???) could look through the Borland side of things to
check if that is the case. Not having Oracle available is obviously a problem, but we could overcome
that problem easily.

Jim Fleming.


Back to top
Jim Fleming
Guest





PostPosted: Fri Mar 05, 2004 1:00 pm    Post subject: Re: ADOCommand Text Editor Access Violation Reply with quote



We have now tried using MDAC 2.8: The AV on closing the CommandText editor now does not occur --
however, an AV occurs the next time you click that property in order to re-open the editor !!! But
now in module msdart.dll !!!!

This certainly looks like Borland misuse of the ADO API routines or interface. Not a MS problem???
Doing the same operations using other OLE DB Providers does not cause AVs, so it could have to do
with complex setting of interface options or whatever -- that's just a guess.

Could someone from Borland look at this to see what is happening ?? I have posted this to Quality
Central 15 days ago with no visible response.

Jim Fleming




Back to top
Jim Fleming
Guest





PostPosted: Sat Mar 06, 2004 10:32 pm    Post subject: Re: ADOCommand Text Editor Access Violation Reply with quote

Brian,
Maybe you are nearer, in some sense, to Borland and so could gently persuade
someone to have a look at this ?? It would be a pity to find, after a lot of
work by others, that the problem really lay at Borland's door, though at
this moment there is no indication either way that that is the case.

On the other hand, I realize that TeamB are volunteers, not Borland
employees. That, and their prompt and usually on-the-ball responses to
varied user problems command respect and appreciation of your efforts. I
hope you keep up the good work, and that Borland recognizes your
contribution to their success.

Jim Fleming


Back to top
joaquim
Guest





PostPosted: Sun Mar 07, 2004 11:25 pm    Post subject: Re: ADOCommand Text Editor Access Violation Reply with quote



Dear Jim:

I was fighting against a very strange problem were the msado15.dll was involved. On some PC the application run smooth on others don't. And the diference was the SP1 service Pack 1 for WinXP, installed or not!!!
I am a newcomer to this things of ADO. I hope that can this help. If so I will be very happy.
My cents.

Joaquim Silva.



"Jim Fleming" <jfleming (AT) euskalnet (DOT) net> wrote:
Quote:
Brian,
Maybe you are nearer, in some sense, to Borland and so could gently persuade
someone to have a look at this ?? It would be a pity to find, after a lot of
work by others, that the problem really lay at Borland's door, though at
this moment there is no indication either way that that is the case.

On the other hand, I realize that TeamB are volunteers, not Borland
employees. That, and their prompt and usually on-the-ball responses to
varied user problems command respect and appreciation of your efforts. I
hope you keep up the good work, and that Borland recognizes your
contribution to their success.

Jim Fleming




Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Databases (ADO) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.