Jump to content

Search the Community

Showing results for tags 'odbc'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Delphi Questions and Answers
    • Algorithms, Data Structures and Class Design
    • VCL
    • FMX
    • RTL and Delphi Object Pascal
    • Databases
    • Network, Cloud and Web
    • Windows API
    • Cross-platform
    • Delphi IDE and APIs
    • General Help
    • Delphi Third-Party
  • C++Builder Questions and Answers
    • General Help
  • General Discussions
    • Embarcadero Lounge
    • Tips / Blogs / Tutorials / Videos
    • Job Opportunities / Coder for Hire
    • I made this
  • Software Development
    • Project Planning and -Management
    • Software Testing and Quality Assurance
  • Community
    • Community Management

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start




Found 4 results

  1. Hi, I had an old D7 + BDE + ODBC -> Sage app that did a simple extract from Sage, did a bit of magic and produced a report. Excellent. We upgraded Sage to V29 and the app wouldn't connect, with a not very useful error message. Excel -> ODBC -> Sage was fine. So I thought I would try with D11 Update 1 + FireDAC. After a few hours of fun (there aren't a lot of ODBC FireDAC examples and I don't have the Sage ODBC driver on my dev box), I got a proof of concept that could connect and I could run an SQL against Sage and get data. To cut a long story short, I built the bare minimum to get the data, save it to XML (Using TClientDataset), load it back up and process the invoice & Invoice_Line tables. The actual bits I want look fine, but then I noticed that some of the data in columns appeared to be the same for the whole column. Many hours later, tracing back through, I go back to my fist example AND "select * from invoice" and then finding invoice 99 Doesn't have the same data as "select * from invoice where invoice_number = 99" FOREIGN_INVOICE_NET="1300" (Actually -5.83 if selected via excel & ODBC or using the specific Where clause) FOREIGN_INVOICE_TAX="260" (Actually -1.17) FOREIGN_INVOICE_GROSS="1560" (Actually -7) INVOICE_NET="1300" (Actually -5.83) INVOICE_TAX="260" (Actually -1.17) INVOICE_GROSS="1560" (Actually -7) I'm a couple of days in now and properly pulling my hair out as they found the problem last week and they need the calculation for the monthly ledger entries to close the month off (read a lot of pressure). Does this ring any bells with anyone, any ideas? My next steps are: - get someone to compile my simple app on the latest D11.3 and see if it has the same issue. - get the data out via Excel and use that as the input to my calcs (a temporary solution and a chunk of work). Thanks for your time and thoughts, Jason Added a short video to demonstrate
  2. A long shot and completely related to my other post about d11-update-1-firedac-odbc-to-sage-returning-wrong-data. If I could make the original connection open then all would be good. Basically when I try and connect to the DB in my old app, I get a generic error. I have turned on ODBC logging, which didn't help. Knowing someone else has it working would mean it was worth trying to get to the bottom of that problem, rather than trying to track down a potential bug in D11. TIA JAC.
  3. Devart, a recognized vendor of connectivity solutions for various databases and cloud services, released the public beta of ODBC driver for NexusDB. The driver can be used to access data in NexusDB databases from various analytics, database management and reporting tools, IDEs and programming languages on Windows (32/64 bit): Excel, Power BI, Tableau, RAD Studio, Lazarus, dbForge Studio, RStudio, and many others. The vendor also notes that Devart ODBC driver for NexusDB provides full support for the standard ODBC API functions and data types and can connect to the NexusDB server directly via TCP/IP. It also supports multilingual NexusDB databases, be it Latin, Cyrillic, or Chinese. As an extra benefit comes cost-effective deployment: the driver is a standalone installation file that does not require the user to install or update any dependencies, while large organizations with hundreds of machines can use the silent install method with an OEM license. Users can download the new driver on the vendor’s website to test it for 30 days for free with the third-party tools. The driver is also available for pre-order. To learn more about the recent release, visit https://blog.devart.com/odbc-driver-for-nexusdb-beta.html About Devart Devart is one of the leading developers of database tools and administration software, ALM solutions, data providers for various database servers, data integration and backup solutions. The company also implements Web and Mobile development projects. For additional information about Devart, visit https://www.devart.com/.
  4. Hi, We are trying to add the functionality to allow the user to change the SQL server password if it is expired. The following code snippet using TFDConnection shows what we are trying to do: FDConnection1.Params.Values['Server'] := 'SQLExpress'; FDConnection1.Params.Values['Database'] := 'TestDatabase'; FDConnection1.Params.Values['User_Name'] := 'testuser'; FDConnection1.Params.Values['Password'] := 'oldpass'; FDConnection1.Params.NewPassword := 'newpass'; FDConnection1.Open; But when we get an error while trying to change it: [FireDAC][Phys][ODBC][Microsoft][ODBC SQL Server Driver] Login failed for user 'testuser'. (Error Code is 18456) Tools we use: RAD Studio 10.2 FireDAC = 16.0.0 (Build 88974) Platform = Windows 32 bit SQL Server 2016 express edition ODBC Driver 17 for SQL server. What we observed is that if we use then it works with a patch in FireDAC units. (While debugging we found that it uses a method TFDPhysMSSQLConnection.CheckPasswordChange which uses a connection to check the SQL versions but by that time the connection was not able to make because of the password expiration. So we commented the code inside "CheckPasswordChange" and then it started to work.) But we are told to use ODBC Driver because Microsoft is not going to support Native Client in the future. Is it possible to change an expired password using FireDAC in combination with ODBC driver.? If that is possible then any advice to fix the problem mentioned above? Kind Regards, Soji Mathew.