I filed one earlier.  Unfortunately, the workaround involves going
through 140+ forms and it breaks the next time someone adds a field.  I
am going to find the cause in the vcl code and see if I can fix it in
the inherited dbedit.  What amazes me is that the users had not
discovered it earlier.  In this case it causes repeated disk writes that
are expensive in time  :-)

David Moorhouse wrote:
A possible work around is

IsModified := DbEdit1.Modified and DataSet1.Modified;

I suggest you file a QC report.

HTH

D

On Thu, 30 Aug 2007 16:25:57 +1200, you wrote:

Ok, found the full symptom.

Its definitely in D7 and D2007 and its a basic functionality failure.

Once the modified is set due to user edit, it is not reset even when posted. Its not reset when scrolled either. Unless the new value is different to the old one. So you keep scrolling and modified remains set until it hits a record where the value of the field is different than before. Similarly when you go into insert mode, some of the edits get their modified set, others do not. In the app this paritcular field normally has the same value, hence it showed up for it.

Bottom line - CRUD

Alister Christie wrote:
It's probably because Modified is a property of TCustomEdit and not related to any data-awareness. From the Help: Use Modified to determine whether the user changed the Text <StdCtrls_TCustomEdit_Text.html> property of the edit control. Modified is only reset to *False* when you assign a value to the Text <StdCtrls_TCustomEdit_Text.html> property. In particular, it is not reset when the control receives focus.

Alister Christie
Computers for People
Ph: 04 471 1849 Fax: 04 471 1266
http://www.salespartner.co.nz
PO Box 13085
Johnsonville
Wellington


Rohit Gupta wrote:
In both D7 and D2007, just on dbedit on one form has a sticky modified property. Once the value is changed, the modified goes to true and stays there. Even after post, cancel or scroll, until the form is killed. Obviously, there is nothing in any event that modifies the value.... only the user does.

Has anyone come across this or can postulate a reason for it ?


--
*Rohit Gupta*
* B.E. Elec.   M.E.   Mem IEEE    Associate IEE*
*Technical Manager*
*Computer Fanatics Limited*
** *Tel*     +64 9 4892280
*Fax*    +64 9 4892290
*Email  [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>**
*Web    *www.cfl.co.nz <http://www.cfl.co.nz/>
------------------------------------------------------------------------ This email and any attachments contain information, which is confidential and may be subject to legal privilege and copyright. If you are not the intended recipient, you must not use, distribute or copy this email or attachments. If you have received this in error, please notify us immediately by return email and then delete this email and any attachments.
------------------------------------------------------------------------

_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
------------------------------------------------------------------------

No virus found in this incoming message.
Checked by AVG Free Edition. Version: 7.5.484 / Virus Database: 269.12.10/977 - Release Date: 28/08/2007 4:29 p.m.
_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe



_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe




_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: delphi@delphi.org.nz
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe

Reply via email to