ADS with 64bit FWH Apps

[TimStone]

Because ADS is no longer supported, and little to no information is on the internet, I have a question for others who use it:

I have a variety of licenses ( 7.0 - 12.1 ). I have them all installed in Windows 64 bit OS. I now distribute my application with both 32 and 64 bit builds with Harbour/MSVC and FWH. 32 bit apps never have an issue. But the identical build in 64 bit receives a "cannot connect" error message on all versions prior to ADS 12.

Does anyone else have experience with this issue running ADS ?

This is not a FWH issue. My clients using the ADS software, prior to 12.0, simply run the 32 bit build of my application. However, it would be nice to resolve this issue.

Thanks for any insight you might have.

Tim

[Enrico Maria Giordano]

It could be a problem with rddads.lib and ace64.lib versions or with ace64.dll version.

[Enrico Maria Giordano]

Do you think that adsloc32.dll and adsloc64.dll are needed? If yes, I will update the Harbour builds again with those DLLs in the dll directory. Please confirm.

[TimStone]

I don’t think those are needed. The last ADS release was 2015. Remote is useful but I find local is slower than the native rddcdx.

I distribute the last .dll files they produced for 32 and 64 bit. Those are usually good with versions 10-12, except for 64 bit on 10 & 11.


Sent from my iPhone using Tapatalk

[Enrico Maria Giordano]

Ok, thank you. Anyway, I forgot that they were already included in the Harbour builds.

[reinaldocrespo]

Hello everyone;

I bet the problem here is that you are trying to connect to an older server version using a newer client version. The opposite is fine. But newer clients need same or newer server.

Try using 64 bit version of ADS 12 if you want to connect to ADS 12 server.

All my customers are version 10 thru 12. But I only use version 10 of the client regardless of server version ( >=10 ). All improvements since version 10 are on the server side and you can execute all of them from any client user the corresponding stored procedure "sp..." function.

Reinaldo.

[NWKL]

Enrico, are you using ads 10 on client side for build xharbour and harbour ? i guess is this the right, because using 10 version in client side we can access 10 or newer version local/server.

thanks

[Enrico Maria Giordano]

I don't know, never used ADS. How can I check which version is used to build [x]Harbour?

[NWKL]

Enrico,
in makefile of x(harbour) :

set version to use:
SET ADS_LIB_VERSION=1010
set directory of ace of this version:
SET HB_DIR_ADS=\Ace\101049


this set to compile build libs with ace 10, this way like reinaldo says we can access to 10 and above local and server.

maybe reinaldo can help us...

thanks

[Enrico Maria Giordano]

Ok, I'll wait for other opinions. I don't want to publish new builds if I'm not sure.

[NWKL]

Some time ago when i build x(harbour) myself, this is ever work, using ace from 10, i can access 10,11,12 versions, but waiting info from others users is good.
you need ace redistributable 10.

very thanks for your time,
best regards.

[Enrico Maria Giordano]

you need ace redistributable 10.

Can you provide me ace.h, ace32.lib, ace32.dll, adsloc32.dll and the same for 64 bit, please?

[Enrico Maria Giordano]

Received, thank you. The 32bit files are identical to mine, so xHarbour 32 bit should be already ok. The 64bit files are different. Can you confirm that I have to use yours to build [x]Harbour? Do you want my files to check them there?

[NWKL]

Enrico, sorry, i use ads in legacy app in 32 bits, i dont use this in (x)harbour)/fwh 64, so i cant help, maybe someone using ads with (x)harbour 64 can help us.

thanks

[Enrico Maria Giordano]

Ok, let's wait for other opinions.