Hans J. Ellingsgaard

My guess is that your tables has a lot of records, or each of your records holds a lot of data, and when you opens it, with a table or query, you get all the records into memory. If that's the case, you will need to limit the number of records with a where clause in your query. You could also limit the number of fields for each record in an overview, and then select all fields only for an active record.

Do you use query or table components?

The table component is not well suited for large datasets. It's better to use a query, and do the filtering with sql.

You can usa an API like https://www.ipify.org to get your public ipaddress. When that is said, this sound strange. Do you have a printer that can be called directly with a public ipaddress, do you not have a vpn or some other secure connection to the office network?

The client dataset has a bookmark method you can use. Also use dataset.disablecontrols; / dataset.enablecontrols before and after refresh, as Attila suggests, to avoid flickering in the dbgrid.

When you use the tcp/ip connection, you must define the server. If you are running you DB on same computer as program, you can use the 127.0.0.1 ip address.

I think that Lajos is correct about that bookmarks are lost when closing the query in FireDAC, but if I remember correctly, it did work in Client Dataset.

I can not see why this should be a problem, you got your ID and stick to it until your record is finally posted to the database. You use it as a primary key on your mastertable and a foreign key on the detail table. The generator is running outside the transactions, and you are guaranteed to get a unique value each time you request for an ID.

You can load Excel sheets into a FDMemTable via Microsoft's odbc drivers.

You could use the Constraints property of the form instead of using the Event. Self.Constraints.MaxHeight := Screen.WorkAreaHeight; Self.Constraints.MaxWidth := Screen.WorkAreaWidth;

Is there a reason why you can‘t use generators?

If I remember correctly, IBX does not officially support Firebird. I would rather go with the FireDAC framework instead. The FireDAC framework also seems to have much higher priority than IBX from Embarcadero.

If you place the dll files manually into the windows system folders, you'll need to run regsvr32 to register them in Windows. If you use the installer it will register them for you. If you place them in your programs root folder, there is no need for registration.

With sql databases always use the query component, you have much more control with it.

One way to get around that datetime field, is to create a View on the datbase, where you cast your datetime field to a date field, and then connect the table component to the view instead of the query. Is there a specific reason why you want to use a table compnent instead of a query?

If you use a FDQuery instead of FDTable, you could cast your datetime field to date. Then you can filter on that date field.

Have you checked in wich folder your dll file is located?

If you use the StartTransaction command, you have to finish it off with CommitTransacton or a Rollback. If you're not using a StartTransaction, the FDConnection will start it for you and make a commit when your datasets are closed.

Yes, the developer edition can run via tcp. Have you checked wich port it's using? You can do that with netstat. You should also be able to telnet the portnumber..

If you connect via tcp/ip, it should not matter where your Interbase binaries are located, as long as the interbase service is running. You also need to check wich port it is running on. Normaly it's on port 3050.

Your problem might have something to do with nested transactions. If your db or your odbc driver don't support nested transactons, make shure there is no ongoing transaction on the same connectionm, before you call StartTransaction. Something like this: if FDConnection1.InTransaction then FDConnection1.Commit; FDConnection1.StartTransaction;

A primary key is a ground rule of relational daatabases.

Your problem could come from the gds32.dll client file. If it's in the windows\system32 folder it will be overwritten with each installation. Not all of them have been backward compatible.

It works fine the opposite way - active at designtime and closed at runtime. I guess that most users use it that way. I allways make shure that all my queries are closed at programstart, and then open them via code.

I have converted from IBX to FireDAC without any problems with the datetime fields. What database are you using?