FiveTech Software tech support forums

I agree. In the meantime, I'm experimenting. Please note that I always used FWH with any versions of BCC without problems. I found a problem in your compile batch and I'm trying to understand it. I found the problem! Please, try this change in the compile batch (buildx.bat): ...

Mr. João Thanks. For now, I prefer to use bcc & xHarbour versions used by FWH for building FWH libraries. I wait till Mr. Antonio takes a decision to use the new versions. No hay problema, Maestro Nages. El Maestro Antonio definitivamente lo usará. ...

Mr. João Thanks. For now, I prefer to use bcc & xHarbour versions used by FWH for building FWH libraries. I wait till Mr. Antonio takes a decision to use the new versions. I agree. In the meantime, I'm experimenting. Please note that I always used ...

Mr. João

Thanks.
For now, I prefer to use bcc & xHarbour versions used by FWH for building FWH libraries.
I wait till Mr. Antonio takes a decision to use the new versions.

For now, I prefer to stay with the older version of xhabour and bcc7. Actually FWH uses these versions to build all FWH libs.
I will wait till these issues are solved.

... to throw some light on this. Looks like we need to make many changes to our standard buildx.bat being used for decades without any issues on all versions of bcc and xharbour. Better if you and Antonio decide and provide a new buildx.bat in the FWH, which works with all earlier and latest versions ...

I will try with bcc7.70 for sure.
FWH has many users using different versions of bcc.
Whatever FWH provides should work with different versions

... send files as attachments. That is possible only due to some low level ( c language modules ) in FWH2310. So, that is not compatible with earlier versions. We provide here a modified version with which we can send messages and also some images optionally. This works with FWH2304. // whatsapp app ...

... was active, the nKey variable returned the value 286, as seen below. http://www.objekt.com.tr/fwh_test/newtest3.png In both versions, there is a code snippet like the one below inside the METHOD KeyChar function.      //      case nKey > 255         // reject unicode chars  ...

... That is the root of this problem. If I go to our DBFCDX RDD, absolutely no problem. If I turn on ADS LOCAL or REMOTE, using the ADS drivers ( all versions ), the problem described in the original post will occur. I think I'll have to use a workaround to avoid this. I have many clients who use ...

... ). Computer 1 ( C1) is my primary programming computer. I am running Windows 11, 23H2. Builds are done with Harbour ( 32 & 64 ), FWH ( latest versions ), and Microsoft Visual Studio Community ( latest builds ). It is a Dell Inspiron AIO. Computer 2 ( C2 ) is a Mac mini, using the M2 processor ...

ertan wrote:New and older versions of FW or SetUnicode() values no differences. same result. Maybe your font set is problem?

There is not any problem fwh 23.07.

New and older versions of FW or SetUnicode() values no differences. same result. Maybe your font set is problem?

... Integration: Again with the Clipper stuff, and it doesn't even know what it was used for. We constantly see new integrations to the most current versions of Windows, and databases, in Harbour/FWH Here is the problem I am referencing. Essentially, the response assumes Harbour/FWH is inferior because ...

Here is the error log. The Calendar dies in the build. As I said, it works perfectly with 2306 and ALL versions prior to that. I rebuilt it exactly the same going back to 2306, to eliminate the possibility of any change in my code, and it works perfectly. For the complete ...