Error Subcode: 1015 [RDD not found]

Chris · Post by **Chris** » Wed Apr 11, 2018 2:55 pm

Just to explain further, there were 3 builds of Vulcan 3 IIRC, they were 301,302 and 303. Then for Vulcan 4 there was only one (surprise!

), 401. When you use dlls from a certain build (301) for example, then all dlls mus be the same build, you cannot use 301 dlls and 302 dlls together.

In builds 302 and 303 there were a few small improvements over 301, but I think we did not touch at all the runtime for Vulcan 4 (401). So it is better if you use 303 or 401, but also 301 and 302 are fine, too (actually even most 2?? builds are fine regarding the runtime).

And as Wolfgang said, that's only until the X# runtime is finished, at which point vulcan will be completely history at last.

Chris

wriedmann · Post by **wriedmann** » Wed Apr 11, 2018 3:06 pm

Hi Chris,

about the X# runtime: AFAIK the Vulcan RDDs need the Vulcan runtime, and both runtimes cannot be used together. Therefore who uses DBFCDX can only jump to the X# runtime when the X# DBFCDX is ready. ( the ADS RDD is no solution because ADS is not compatible at 100% with the DBFCDX RDD, for example you cannot use own functions in the index expressions).

Wolfgang

ic2 · Post by **ic2** » Wed Apr 11, 2018 5:58 pm

I do use the Vulcan DLL's version 3.0.303.0. The 2 ADS packages (Advantage_RDD_301_F2F4.zip and Advantage_RDD_302_F2F4.zip) contain 4 different AdvantageRDD.dll; 1 per file for ADS 10 and 1 for ADS 11. Remarkably both versions seem to be 11.10.0.10 but with different dates 11-10-2014 and 12-8-2013. As I have a 11.10.0.20 I think there's some other issue because that clearly seems newer.

This works provided the ADS.INI, ace32.dll, adsloc32.dll, axcws32.dll, AXDBFCDX.RDD and AXSQLCDX.RDD are of the same date 27-11-2012 and copied in project directory and binrelease + binDebug directories. And referred to in VS of course. This seems to have been the issue today for a large part. Now it looks that it works on the Azure server with local server and tomorrow we test at the clients server with ADS remote installed, on which I'd say it should work too.

Thank for all the explanation.

Dick

ic2 · Post by **ic2** » Wed Apr 11, 2018 6:04 pm

Hello Wolfgang,

You wrote:

"the ADS RDD is no solution because ADS is not compatible at 100% with the DBFCDX RDD, for example you cannot use own functions in the index expressions)."

I wasn't aware of that. This is also in VO I suppose? I don't think I use user defined functions in indexes so in that case the ADS RDD is the solution.

Dick

wriedmann · Post by **wriedmann** » Thu Apr 12, 2018 5:09 am

Hi Dick,

it tooks me about a day of work to make some of my applications compatible to ADS.
There are several things I'm using that don't work with ADS: like an index expression on a substring of a memo field, using own functions in index expressions, and some limits in the filters. And try to save an Euro sign in a character field: you will not be able to retrieve it after - you will see another character. That has to do with the ANSI conversion that ADS requires.

ADS is really a good choice: it is stable and works very well, but unfortunately SAP seems to abbandon it. It has saved me one of my largest projects (without ADS I had to rewrite several VO applications to SQL in no time and for no money).

But again: it is not compatible at 100%.

Wolfgang