Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread DBaware components loose Datasource reference
Sat, Apr 13 2019 9:13 AMPermanent Link

Anthony

I have noticed a few times now that for some reason which I can’t identify my DBaware components lose their Datasource reference, just wondering if anyone else has encountered this or knows the reasons why this may have started happening in my environment.

I'm using Delphi Rio 10.3.1, EDB 2.31b1 and the controls which are losing their Datasource references have the Datasource on a separate Datamodule.

This is only happening to some controls and only occasionally, the Datamodule contains TEDBQuery components for config and lookup fields so when the Datasource reference gets deleted it is not immediately obvious there is a problem and since not all the controls are effected it is time consuming to verify each form so any help would be much appreciated
Wed, Apr 17 2019 2:39 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Anthony,

<< I have noticed a few times now that for some reason which I can’t identify my DBaware components lose their Datasource reference, just wondering if anyone else has encountered this or knows the reasons why this may have started happening in my environment. >>

This sounds like a Delphi issue, but, in general, I try to keep the TDataSource instances on the forms, and the core TDataSet-descendant components (and ancillary components) on the data modules.  However, if the issue is with data-module linking, in general, then you might just have to bite the bullet and make sure that you keep the data module always open with the project.

Tim Young
Elevate Software
www.elevatesoft.com
Thu, Apr 18 2019 4:07 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Anthony


Now Tim has posted that its jogged my mind. My applications generally have the main form and the datamodules set to open automatically with the datamodule opening before the form. I still have to open the datamodule in the IDE to be able to access the tables etc on it, and I do occasionally lose the linkage, generally fields but sometimes the datasource, or the dataset in the datasource.

Roy Lambert
Tue, Apr 23 2019 10:29 AMPermanent Link

Anthony

Thanks Tim & Roy

I'll move the Datasource components to the forms and leave the edbquery components on the datamodule to see if that is any better.

Roy, do you remember how you get the datamodule to always load with the project? I have found "Save project desktop when closing" in the Tools, options menu but this seems to be for all projects and if I ever close the datamodule when this is ticked i'm back to the same issue

Thanks

Anthony
Tue, Apr 23 2019 7:09 PMPermanent Link

Steve Gill

Avatar

Hi Anthony,

<< I have noticed a few times now that for some reason which I can’t identify my DBaware components lose their Datasource reference, just wondering if anyone else has encountered this or knows the reasons why this may have started happening in my environment.

I'm using Delphi Rio 10.3.1, EDB 2.31b1 and the controls which are losing their Datasource references have the Datasource on a separate Datamodule.

This is only happening to some controls and only occasionally, the Datamodule contains TEDBQuery components for config and lookup fields so when the Datasource reference gets deleted it is not immediately obvious there is a problem and since not all the controls are effected it is time consuming to verify each form so any help would be much appreciated >>

I think this issue has been in a few Delphi versions. I no longer use data-aware components but I remember this happening as far back as Delphi 7.  I used to use a data-aware grid and it would lose the Datasource reference.  It was quite embarrassing when a new version of the app was release and the grid was empty.

Another annoying bug I have seen with Delphi is that the EngineType property of the TEDBEngine component will sometimes switch to etClient in my custom server, and to etServer in the client application.  I now set these in code just to be sure.

= Steve
Wed, Apr 24 2019 2:57 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Anthony


>Roy, do you remember how you get the datamodule to always load with the project? I have found "Save project desktop when closing" in the Tools, options menu but this seems to be for all projects and if I ever close the datamodule when this is ticked i'm back to the same issue

I don't - I just try and remember to open it after opening the project Frown

Roy
Wed, Apr 24 2019 7:21 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Anthony


Almost certainly unrelated but I just lost my GExperts' settings.

Roy Lambert
Fri, Apr 26 2019 5:13 AMPermanent Link

Anthony

Roy Lambert wrote:

>Almost certainly unrelated but I just lost my GExperts' settings.

Are you using Rio? I'm starting to think the issues started after I upgraded to 10.3. The day after my Emb. subscription renewed I had to rebuild my development PC as the IDE keep quitting with Stack Overflow error and support said it was due to a 3rd partly library, today my IDE is showing range check error on startup.

I've checked my other projects and they most have the Datasource and table/query components on Datamodules and never experienced this data loss in Delphi projects files like this in 20 years
Fri, Apr 26 2019 5:58 AMPermanent Link

Charles Bainbridge

FWIW, I had a similar problem with the populated DatabaseName property on TEDBDataset-type components getting emptied on loading projects. I have a design time package containing descendants of EDB table and query objects which hadn't been rebuilt after installing a new EDB build.

I had to uninstall the new IDE Navigator add-in from my Rio IDE as it was causing big problems, crashes principally.
Sat, Apr 27 2019 4:06 PMPermanent Link

Anthony

Charles Bainbridge wrote:

> I had to uninstall the new IDE Navigator add-in from my Rio IDE as it was causing big problems, crashes principally.

You might be on to something with the Navigator plug as I did recently install it with Rio 10.3.1, I'll uninstall and see if that improves things.
Image