shun

I have some slightly outdated information, but it was mentioned that versions prior to C++Builder 6 could be converted into an automatically convertible format by first opening them in version 2007. I found this video that discusses it: 「Delphi/C++Builderマイグレーション作業を手間をかけずに完了させる方法」 第1回「コード」 - YouTube My question is: Do I need to go through this step with the latest version, C++Builder 12, in order to convert older versions?

thank you!

thank you!

Hello, I am currently considering migrating a project developed with C++Builder. In this project, we are using both third-party and custom components, and I would like to assess their impact on the migration. Could anyone suggest tools or methods to identify these components effectively? C++Builder: Version 5, Enterprise Edition Any guidance would be greatly appreciated. Thank you.

Hello, I am currently using C++Builder 5 Enterprise Edition for an internal system, and I would like to upgrade to the latest version of C++Builder to verify compatibility and ensure smooth operation. However, I am considering using the Community Edition for this testing phase. Could you please let me know if the Community Edition is suitable for verifying compatibility and functionality of an application originally built in C++Builder 5 Enterprise Edition? Are there any limitations I should be aware of when using the Community Edition for such purposes? Thank you for your assistance!

Thank you. It was very helpful!

Environment: C++Builder 5.0.12.34 OS: Windows 10 Pro I came across a statement that BDE (Borland Database Engine) is an outdated architecture, and its functionality on currently released Windows OS versions is not guaranteed. However, I couldn't find specific information on which versions of Windows it was last confirmed to work with. Additionally, as I consider upgrade to the latest version of C++Builder I would like to know if migrating to FireDAC is essential or not. Could anyone provide clarity on these issues? Also, if you have any resources or references regarding BDE compatibility, I would greatly appreciate it.

Environment: C++Builder 5.0.12.34 OS: Windows 10 Pro I am currently in the process of updating our C++Builder project and need to transition from using ANSIString to UnicodeString, as the string type in the RTL has been mapped to UnicodeString in the latest versions. To ensure a smooth migration, I need to identify all the places where we use: ANSIString or char-based strings. Functions that count characters based on the assumption that 1 character equals 1 byte (such as those working with strlen or similar). Any C-language derived functions (e.g., strcpy, sscanf, fopen) that need to be replaced with their wide-character counterparts (e.g., wcscpy, swscanf, _wfopen). Literal strings that need to be prefixed with L for wide character support. Could you provide guidance or tools to help identify all the necessary changes to make for this transition?

I am currently using C++ Builder version 5.0.12.34. I would like to migrate to the latest version, but I believe code modifications will be necessary. Could you advise me on how to investigate and identify the necessary modifications?

Environment: C++Builder version: 5.0.12.34 OS: Windows 10 Pro Currently, I am using BDE to connect to the database. As I am planning to update C++Builder to a newer version, I should migrate to FireDAC. What steps should I follow to achieve this?

Thank you for the useful link! I appreciate the suggestion about the reFind utility—it sounds like a helpful tool. It's good to know it has templates for BDE-to-FireDAC migration.

You recommend migrating to the Clang compiler, but I feel that continuing to use the Classic compiler might be more beneficial since non-standard coding practices that worked with the Classic compiler might not work with modern C++ under Clang. Could you explain the advantages of migrating to Clang

Thank you for your response. Could you tell me how to check if there are any features that are exclusive to the 'Enterprise' edition?