FiveTech Software tech support forums

1) Important: Please do not use FIELDS clause. This was originally meant to facilitate easy migration from WBrowse. Using COLUMNS clause allows us to to take full power of XBrowse. Using FIELDS clause makes XBrowse dumb 2) If we want to specify all columns of the DBF, ...

... to HARBOUR. I think it would also be wise in terms of mod harbour. Have you ever considered a changeover? Best regards, Otto Dear Otto, The migration from xHarbour to Harbour is quite simple and easy to be done. mod_harbour is based on Harbour as it requires robust multi threading, which ...

Dear Ari,

Please let us know if you need any further help on your migration

We are here to help you

... and sockets management we need to use threads and xHarbour threads support does not work as expected. It is a serious technical limitation. The migration to Harbour is really easy. You should have all your apps working with Harbour in less than one week. You have all our support and help to ...

... the syntax: ADD TO oBrw for creating columns as obsolete. This command was created many years back for compatibility with TCBrowse for easier migration from TCBrowse to TXBrowse. Same way, please do not use the FIELDS clause for similar reasons. Instead use COLUMNS syntax. Better avoid them ...

... Tim Some years ago I moved from ADS to MySql. This was the best thing I did. Mr Rao did a great job with FWH MySQL/MariaDB native support, the migration from ADS was very easy and his support is fast and perfect!

... "valN" } } ) also works. Soon we are going to implement lThrowError like functionality. May I know what do you advise to make migration easlier?

Hello everybody.
I'm thinking about migrating from 32 to 64 bits, and researching on the subject I found this topic, which is a good tutorial on how to do this.
But a question that remains is: Are there any performance gains and other improvements that are worth the migration?

Recommendations: Please avoid using ADD COLUMN TO oBrw. This syntax was created long time back only to help easy migration of already existing code from TCBrowse. Also we better inform the xbrowse that the datasource is the array while creating the browse. Recommended syntax: aData ...

very good

Yessssss !

It work nicely !

Thanks,

JF,

Please try this new build and let me know how it works:

https://github.com/FiveTechSoft/mod_harbour/blob/master/fastcgi/windows/win64/ADS/modharbour.exe

Hi Antonio,

Any plan to also recompile the ADS version of Modharbour.exe ?

Thanks,

JF

many thanks for your great feedback

Hi Antonio,

Renaming libcurl-x64.dll into libcurl.dll solved the problem.

Last Modharbour.exe is working fine now with ADS, with and without using WAPI_LOADLIB...

ADS64 11.1 dlls are all copied into the same folder as modharbour.exe

Many thanks, you are the best, as usual

JF