FiveTech Support Forums

Tim,

Lets use and focus on Harbour, its the best way to go

What problems do you have with Harbour and ADS ? I may have missed that post from you, thanks

Antonio,

With xHarbour ( .com ), Dmitri Costenco provided me with and ads.lib that works with xHarbour and ADS 7,8,9 ... and it also works fine with ADS 10 and 11. I have stayed with older functionality in ADS so I didn't add new features found in newer ( 10 or 11 ) versions. My program, built with xHarbour, can work fine on all servers from ADS 7 to 11.

For Harbour, I have to use rddads.lib and it is only working properly on the newer versions. I believe at 9 they made some changes in ADS, and the backward compatibility was not included in the Harbour code.

So, I have ADS 11 on my computer for testing, and all works fine. But, if I put it on a computer with ADS 7 or 8, all fails.

Tim

Timm,

What fails do you get?.

In the old installations, have you tried to use ADS 7/8 with latest ACE client .dlls?.

Lucas,

I don't have the exact error message now but it fails to even initialize the program.

I have the ADS .dlls installed on each location according to their version. I can't use the latest ( Version 11 ) .dlls on a Version 7 ADS.

I ran into problems with ADS when I first started working with Harbour and posted to their forum. The response I received was that they only supported the latest version of ADS. If I tell my clients they have to upgrade their server software, they will start looking at my competitors' products. That is not helpful.

I am linking in the RDDADS.lib and ACE32.lib from the Harbour build Antonio provided for MSVC.

Tim

I have the ADS .dlls installed on each location according to their version. I can't use the latest ( Version 11 ) .dlls on a Version 7 ADS.

Its the other way around. A program written for ADS 7 will work on the newer versions but newer drivers are not compatible with older systems.

The error I receive with the MSVC / Harbour version is:

"The ordinal 508 could not be located in the dynanmic link library"

This occurs when trying to start the program. I just installed ADS 8.1 on my computer so I can test this.

Tim

Tim,

Lets try to know what DLL the app error message refers to.

If there are several ADS DLLs, please rename them, one by one, and run your app until we find which DLL it is.

There are two ways to refer to an external DLL symbol, so I think a workaround is workable

Antonio,

For the ADS Remote server, there are two .dll files, and they must match the server. They are ACE32.dll and AXCws32.dll. The other two are "local"

These are not the problem !

There are two libs we must link in. One is ace32.lib and the other is rddads.lib. The problem likely lies in the rddads.lib.

When I encountered this before, I was told that the rddads.lib is designed to work with the current version of ADS only. Apparently there was a call placed in that library to something referenced with the "ordinal 508". This might have been a capability that was found in the newer versions of ADS.

The issue won't be resolved with new .dll files. They have to be matches for the version and I have those correct. They all work correctly with xHarbour.

Tim

Timm

If you use latest dlls in your application, which also correspond with latest rddads.lib, you will be able to connect to all servers since 6.0 to 11.

Lucas,

What are the "latest" .dlls.

I have the following in my version of Harbour from Antonio:

ace32.lib dated 12/15/2011
rddads.lib dated 5/16/2012

There are no harbour supplied .dll files.

When I tried to use the ADS 11.0 .dll files, I received an error saying they are the incorrect version.

Tim

Timm.

Ace32 is not the latest.

Please, donwload latest ARC and copy from there.

Also, I suggest to generate also newest libs installing the SDK c. files.

Norberto,

All operating system have viruses. All of them

Congratulations for your tablet and thanks for helping doing some tests for Harbour on Android. If these tests are fine, the idea is to port it to WinRT and IOS.

Maybe a dream ? Lets see

Tim,

If the ordinal error reason is as you describe it, then we could try to build previous versions of rddads until we identify which function is the one that causes that error.