Stano

In my opinion, this is a typical example of failure - bad logic. Simply, the user cannot/must not enter such a combination. You have to solve that on the client.

If I'm not mistaken, there is some time limit to get the lower versions. Did you not cross it?

Turn on automatic saving.

It would be more correct to create the form only at the moment of need. Of course, this also depends on the logic of the program.

----

I'm pissed too. They have stated on the WEB that the problem is solved. RSP-39640. https://quality.embarcadero.com/browse/RSP-39640 Try turning off error insight. Then that's how it works. It's not off my mind. It helped me. It can be lived with.

I couldn't find a better picture.

Sometimes I get the Fx keys to lock up. Try to unlock them. I have a "Lock" key for that

error1.jpg. I'm just guessing to the best of my knowledge. Is Tbasicdm a TDataModule? The parameter is of type TForm. I don't know if they are interchangeable.

I don't know the answer. But many programmers use Subform because of problems with Frame. They have no problem with that. Me neither. Maybe it's better to go the Subform route.

If they are connected to the DB table and it is open, then their state reflects the state of the field for the current record! It must be so. Try it: Set them to show 3 statuses. DataSource.Enabled = False.

Will setting all affected DB table fields to False (or null) help?

I recently read that only .Free should be used to release the form

They all tell you the same thing: check the data and then generate the XML. It's exactly the same procedure as with DB data, or anything else.

That window is not new. I did not use anything other than that window to place the cursor in the place of the bookmark. Note that you can view all bookmarks in open files in that window. The main thing is to set the content of this window correctly.

In similar cases, I basically set the value of the field. My experience: changing the value of the component (DB TMS) does not change the value of the DB field. I assume that the appropriate event is not triggered, because it happens programmatically. I don't consider it a mistake. If I change the value of the DB field, the components always respond correctly. For me, it doesn't really matter what I set. I have significantly longer text when writing to the DB. For that write-up, I use the given component directly and NOT the DB table.

Hi, Subform for "List". The structure is always: PrimaryKey Title The problem is that if I don't create the fields, the names are ''. This is a problem for the function function TjstIBCNavigator.LocateRecord(const PKeyValue: Integer; const FieldIdx: Integer = 0): Boolean; begin if FieldIdx > 0 then FPKeyName := FDataSource.DataSet.Fields.Fields[FieldIdx].FieldName; // Here I get '' Result := FDataSource.DataSet.Locate(FPKeyName, PKeyValue, [loCaseInsensitive]); // Failure of course end; If I create them, I get them when I open the table Field.Data Type cannot be set because it is Read Only. How can it be solved? I might throw a chart in there just in case. This is not clean and especially not universal!

Thank you for your response I have already found out where the basic problem is. In my component. I used the solution using separate tables and the problem ran out for me right away.

I don't know how to do that example. Leave it at that. At least I'll describe what I'm trying to do. I have tables with a structure Primary key Title I am trying to create a single subform that would apply to all tables. I have (one each) TIBCDataSource and TIBCTable on it. I would like to modify the TIBCTable on run time as needed. My attempt: procedure TCollection.SetTable; begin FTable.TableName := FDataCollection.TableName; var FldName := 'ID' + FDataCollection.TableName; FTable.IndexFieldNames := FldName; FTable.Fields.Fields[0].FieldName := FldName; FTable.Fields.Fields[0].Name := 'intgrfldCollection' + FldName; FTable.Fields.Fields[0].DisplayLabel := FldName; FTable.Fields.Fields[1].Size := FDataCollection.TitleLength; end; I can not do that. I set the parameters before opening the table I will programmatically open the table. I have no idea when it will actually open On Locate, the original name is loaded in FDataSource.DataSet.Fields.Fields[0].FieldName It cannot be changed on an open table I probably have no choice but to use a separate table for each case.

Such a solution came to his mind at design time, use one table and generate fields in it at runtime set properties that change They are mainly Name of the table Name of the first field - primary key That should work in my opinion.

OT: It is only 516 MB

One reason is that the DB is open in another program. You have a DB set as embedded and it is already open, e.g. in the DB manager. If I missed it, other discussants will describe other scenarios.

There was a time when it happened quite often. It stopped by itself.

I just realized that I wrote it the other way around. Just change the *.dfm. No *.pas. I apologise.

That was in D10. I didn't do that in D11.