Jump to content

gkobler

Members
  • Content Count

    181
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by gkobler

  1. gkobler

    TFDUpdateSQL Problem

    Thanks for clarifying and investigating. Attached my smal demo project. Just start it and try to change a value at any field. Immediately when you try to post this chages, the exception are raising. Quality portal is still in read-only mode, so i can't report the bug. FireDac Sample.7z
  2. gkobler

    Interbase - unable to start service

    May do you have installed Firebird-Server at the same PC?
  3. gkobler

    wuppdi Welcome Page for Delphi 11 Alexandria?

    Fixed I've already thought about implementing it. But I'm very busy with other things at the moment. But I think I will do it.
  4. gkobler

    wuppdi Welcome Page for Delphi 11 Alexandria?

    I did not find any info at the stacktrace that the WP-Plugin made the error. There is no entry of my WP-Plugin. But try to compile and install the follow demo, and look if the same exceptions are happend C:\Users\Public\Documents\Embarcadero\Studio\23.0\Samples\Object Pascal\VCL\VCL WelcomePage\ToolsAPI.WelcomePage Basic PlugIn This demo are the basis of my WP-Plugin
  5. gkobler

    wuppdi Welcome Page for Delphi 11 Alexandria?

    Use the same version. At the moment I can't even imagine what could trigger such an exception in my plugin in connection with TMS.
  6. gkobler

    wuppdi Welcome Page for Delphi 11 Alexandria?

    Hello @AJ_Oldendorf I have open your demo, but can reproduce the case. šŸ˜ž When i click to the described area, it selects PageControl1, right?, After Ctrl-C nothing happens, also when i close the form.
  7. gkobler

    wuppdi Welcome Page for Delphi 11 Alexandria?

    Hello @AJ_Oldendorf will investigate the case. I have TMS-All-Access. But the next two weeks iā€˜m not in the office. And i think this case could be complicated, we will see
  8. gkobler

    Firebird 3.0 problem

    find some other links in the google firebird-support group See the Firebird 3 release notes. Connection strings that are only a file path will now use embedded. See https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rlsnotes30.html#rnfb30-engine-modes-protocols and https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rlsnotes30.html#rnfb30-compat-winlocal Also read https://www.firebirdsql.org/file/documentation/release_notes/html/en/3_0/rlsnotes30.html#rnfb30-engine
  9. gkobler

    Firebird 3.0 problem

    OK, there are some infos about embedded from Helen and Vlad read the PDF https://www.firebirdsql.org/en/news/embedded-server-in-firebird-3/ May that have some infos for you.
  10. gkobler

    Firebird 3.0 problem

    Shouldn't the client library be called embeded.dll instead of fbclient.dll? And as far as I know, the Firebird installation must be in the Project.exe directory. But I could be wrong.
  11. gkobler

    Delphi 12 and *.dsv

    This options are new in D12
  12. gkobler

    Delphi 12 and *.dsv

    have the same files, i look like there where store some information of the open files
  13. gkobler

    Delphi 12 IDE, auto-formatter mutilates generics

    I'm just lazy and like to leave the work to the formatter
  14. gkobler

    Delphi 12 IDE, auto-formatter mutilates generics

    Is there an alternative for the code formatter?
  15. I have a MSSQL Connection via FireDAC with D12 and the newest ODBC Driver 19.3.2 The connection to my MS-SQL Server 2017 is working. Many Select Statements are running well, but when i execute an Update Statement via TFDCommand component i got the follow exception. [FireDAC][Phys][ODBC][Microsoft][ODBC SQL Server Driver]Connection is busy with results for another hstmt I have no problems at my developper PC, this happens on the customer PC! does anyone have any experience with this? Thankfull for any hint. Gregor
  16. i can't check that, because on the productivity server i can't play and on my developer PC it has no made any problems. So the server on my customer and my MS-SQL Express test enviroment must have some differences.
  17. I looked at the task and tried some of the things described there, but none of it helped.
  18. I only had the FDQuery open and FDCommand was then executed in the While Loop. Nothing else, as shown in the example, I only deleted the Firebird statemens, but this is a different FireDAC connection. What kind of driver is it that can't even manage an open query with an UPDATE statement at the same time?
  19. I tried Yes and No, No diffenrence same exception I had V17 first, then i made some changes with D12 and i got the truble. After that i updated to V19.3.2
  20. Meanwhile i have a workaround for my problem. I changed my code to the follow fdcAmmann.Open; TRY fdqImportData.Open; fdmtImportAmmann.Data:= fdqImportData.Data; fdqImportData.Close; fdmtImportAmmann.Open; fdmtImportAmmann.First; WHILE NOT fdmtImportAmmann.Eof DO BEGIN ... some other code to store the data to a Firebird database ... fdcUpdateAmmann.CommandText.Clear; fdcUpdateAmmann.CommandText.Add(Format('UPDATE dbo.TDexAllocationTicketOut SET ReadDT = GETDATE() WHERE IDInt = %d', [fdmtImportAmmann.FieldByName('IdInt').AsInteger])); fdcUpdateAmmann.Execute; fdmtImportAmmann.Next; END; fdmtImportAmmann.Close; FINALLY fdcAmmann.Close; END; the main changes are, first i open the FDQuery and copy the data to a FDMemTable, after that i close the FDQuery and my While loop are working with the TDMemTable dataset to with the query. So i got no exception and the UPDATE Statements is working well. Strange...
  21. Have added the TFDMoniFlatFileClientLink component, and als added the parameter to my MSSQL connection 'MonitorBy=FlatFile' But when i open my connection, i got now the follow exception You can try to run the program with F9, but it hangs. I think FBMonitoring are buggy
  22. Unfortunately, I do not have access to the server, which is managed by another company. I can ask if they see anything and if they can turn off MARS on the server side. I'm not sure if it could have something to do with D12. Because it used to work. But with D11.3 and older ODBC drivers. And there were also Windows updates on the PC and I don't know if there were changes on the server.
Ɨ