Well, at least now you can tell your customer that after long hours of analysis and optimisation you have developed a workaround and improved the performance of your application a thousandfold :-)
-----Original Message----- From: vss [mailto:[EMAIL PROTECTED] Sent: Friday, April 02 2004 10:04 a.m. To: NZ Borland Developers Group - Delphi List Subject: RE: [DUG] ADO Weired ness oh...F&^%% !!!! you are SO right! agh.........what a MORON ! that will be why....well. it fixes why it builds up to 20 seconds ! I am going home....obviously today is going to be bad..might as well quit now....hehehe....Thats Steve...... Jeremy -----Original Message----- From: Steven Knight <[EMAIL PROTECTED]> To: "'NZ Borland Developers Group - Delphi List'" <[EMAIL PROTECTED]> Date: Fri, 2 Apr 2004 09:53:43 +1200 Subject: RE: [DUG] ADO Weired ness > Don't you need to do a 'clear' before you do the 'add' ?? > > > -----Original Message----- > > From: vss [mailto:[EMAIL PROTECTED] > > Sent: 02 April 2004 9:35 am > > To: [EMAIL PROTECTED] > > Subject: [DUG] ADO Weired ness > > > > > > Hi All. > > We have been tracking down a problem that had occured off and > > on with an > > app. we have written that used ADO. > > Basically it was comming up with Times outs, and I FINALLY tracked it > > down to the ADOQuery CommandTimeout which is because of an > > internal issue. > > Anyway, we fixed the internal issue (hardware), but I have > > left a wee app > > running all yeasterday and overnight, and then today when I > > got to work, > > its had gone from like milliseconds to do the insert, to 20 seconds ! > > Its seems to just increase over time. > > All I am doing is :- > > > > ADOQuery1.close; > > ADOQuery1.sql.add('UPDATE TESTTABLE SET TEST = TEST+1'); > > ADOQuery1.ExecSQL; > > > > And thats it. Oh this gets triggered on a timer that fires after 10 > > seconds. > > > > This seems really strange if not BAD behaviour of the control. > > > > Anyone seen this before? or have any suggestions. > > I am going to try actually creating the query object each > > time it needs > > to use it and then free it when its finished, but this seems > > a bit over > > the top. > > I think its the problem with out app. and why I have never > > been able to > > reporduce it. I.e. the client doesnt close the app. down, > > because they > > operate 24/7 and then they say its slow, and they get the > > time out error. > > > > Jeremy > > > > _______________________________________________ > > Delphi mailing list > > [EMAIL PROTECTED] > > http://ns3.123.co.nz/mailman/listinfo/delphi > > > > > Visit us online at http://www.ecan.govt.nz > > > > ********************************************************************** > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you have received this email in error please notify > the system manager. > > The contents of this email and any attachments are not formal > policy of Environment Canterbury, unless otherwise stated. > ********************************************************************** > > _______________________________________________ > Delphi mailing list > [EMAIL PROTECTED] > http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
