Re: [DUG] Finding all instances of a component where a property has notbeen set

Mon, 09 Sep 2013 22:09:31 -0700

Hi

Yes In cases where the component is on a data module.  Basically the component is a Query component and should be linked to a database / connection component.  There is one of these in the app and all db components should connect to this.  However it appears that some old components (possibly from when the app was BDE based) didn't have that set and had just defaulted to the 'Default' connection.  The updated component version now nicely reports this as an error.  So instead of searching for all times this error occurs I would rather do a dfm search (all components created in code are correctly instantiated) .

Cheers
Rob


On 10/09/2013 4:46 p.m., Jeremy Coulter wrote:
so have you hard coded the property on the control itself rather than in code ?

Jeremy


On Tue, Sep 10, 2013 at 4:26 PM, Robert Martin <[email protected]> wrote:
Hi

I don't think they were ever set correctly.  Might have to make a tool
to deal with it!

Cheers
Rob


  On 10/09/2013 3:02 p.m., John Bird wrote:
> I have a tool that can search DFM too, but it can find where a property is
> set, not where there is no setting.
>
> I do know this problem, have seen a large program (D5) where occasionally a
> navigation control datasource setting was lost.   Because there were so many
> data modules this was a real nuisance, I found the best way was to compare
> all the DFM files with the SVN repository where the settings were known to
> be correct and that often saved a pile of time - and also showed what the
> correct setting was as well.
>
> Of course if the setting has never been there then you have to do something
> smarter and a special tool may be needed.
>
> John Bird
>
> -----Original Message-----
> From: Robert Martin
> Sent: Tuesday, September 10, 2013 12:16 PM
> To: NZ Borland Developers Group - Delphi List
> Subject: [DUG] Finding all instances of a component where a property has
> notbeen set
>
> Hi all
>
> We have a large app where there are some components (database connection
> components) where a property has not been set but should have been.  A
> recent component update by the author has bought this to our attention,
> now we just need to find all of them and fix.
>
> I have a tool to search dfm files but in this case we want to find only
> instances of a component without an entry for a property.  Is there an
> easy way to do this or do I need to build a tool?
>
> Cheers
> Rob
>
>
>
>
> _______________________________________________
> NZ Borland Developers Group - Delphi mailing list
> Post: [email protected]
> 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: [email protected]
> Admin: http://delphi.org.nz/mailman/listinfo/delphi
> Unsubscribe: send an email to [email protected] with Subject: unsubscribe
>
>
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3392 / Virus Database: 3222/6650 - Release Date: 09/09/13
>
>

_______________________________________________
NZ Borland Developers Group - Delphi mailing list
Post: [email protected]
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: [email protected]
Admin: http://delphi.org.nz/mailman/listinfo/delphi
Unsubscribe: send an email to [email protected] with Subject: unsubscribe


No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3222/6650 - Release Date: 09/09/13




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

Reply via email to