Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
Fields Editor Popup |
Thu, Jan 7 2010 4:38 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
There seems to be a degree of persistence in the field definitions in the IDE when I use the fields editor popup (or whatever you call the little dohicky that pops up when you double click a table). I can delete a field in EDBManager but when I use ctrl-F to repopulate the popup the deleted field(s) are still there. It takes opening and closing each table component to get rid of the deleted fields. IE if I have 2 or 3 table components all pointing at EMSearches on different forms I have to open/close each of them. D2006 & EDB 2.03 Build 6 Roy Lambert |
Thu, Jan 7 2010 1:55 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< There seems to be a degree of persistence in the field definitions in the IDE when I use the fields editor popup (or whatever you call the little dohicky that pops up when you double click a table). I can delete a field in EDBManager but when I use ctrl-F to repopulate the popup the deleted field(s) are still there. It takes opening and closing each table component to get rid of the deleted fields. IE if I have 2 or 3 table components all pointing at EMSearches on different forms I have to open/close each of them. >> Yes, this has been this way since D5 and earlier. It's just the way that the FieldDefs work - they have a flag called Updated that is set in the base TDataSet layer whenever the FieldDefs are updated, and this flag is not reset until the table is opened again, thus the FieldDefs won't change once they have been loaded at least once, and the table has not been opened. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jan 7 2010 2:02 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>Yes, this has been this way since D5 and earlier. It's just the way that >the FieldDefs work - they have a flag called Updated that is set in the base >TDataSet layer whenever the FieldDefs are updated, and this flag is not >reset until the table is opened again, thus the FieldDefs won't change once >they have been loaded at least once, and the table has not been opened. Ah. Obviously it just surfaces in my attention every now and again. I'll try and remember the next time it annoys me, but no guarantees Roy Lambert |
This web page was last updated on Sunday, May 5, 2024 at 10:18 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |