Hi,

Using IBO 5.3.5 [Build 1996] (rev 2015) , Delphi XE2.
I'm currently having a problem getting the message in the subject popping up at regular intervals. It only happens for the legacy TIBOTables in the application. Al the TIB_xx components do not have this problem.

Before each compilation I have to go through the whole project and check the IB_Connection property. 
If the original connection was named cnFB then the error occurs when the IB_Connection has been changed ( not by me ) in the IDE to cnFB (default).
Some code in the component in design mode must be changing this?

Changing it back to the original value,  the application does not have this error.

Saving the project can sometimes do this, but not every time.

Any clues/info appreciated
Cheers
Cam


DFM deatils for the connection are

object cnFB: TIB_Connection
    CacheStatementHandles = False
    SQLDialect = 3
    Params.Strings = (
      'SERVER=localhost'
      'PROTOCOL=TCP/IP'
      'PATH=diary'
      'CHARACTER SET=NONE'
      'BUFFERS=<default>'
      'SQL DIALECT=3')
    Left = 576
    Top = 24
  end

Anyone?

For a TIB_Connection assigned to a TIBOTable, what is the difference between
TIBOTable.IB_Connection := TIB_Connection.Name which is what The source code originally contains and
TIBOTable.IB_Connection := TIB_Connection.Name (Default) which is what The XE2 and IBO design time code decides is required sometimes.

When TIBOTable.IB_Connection := TIB_Connection.Name  no exceptions occur.
When the IDE decides it time for
When TIBOTable.IB_Connection := TIB_Connection.Name (Default) the Transaction is not valid for the current connection exception occurs.
 
Having 30 ish TIBOTables in many data modules in this legacy project, and having to edit each tables IB_Connection property is consuming time which I do not have at this stage of the project.

I can change all IB_Connections on the dev pc, sometimes get an executable without the error, save, commit to the Source repo.
On the build pc which extracts the latest version from the repo, tested 16 times this morning, 11 executables had the exception. In each of these 11 cases the IB_Connection had been changed to add the (Default) to the original IB_Connection! Why?

Thanks in advance for any clues
Cam