|
I posted this in the FireDAC forum and Dimitri say ask Advantage. I think it's a FireDAC issue, but just in case anyone has any insight into this... (thanks) Do I need to set anything up pre-compiling to have FireDAC use v9.10 or Advantage components. I thought I had successfully converted from the ADS comps to FireDAC comps as everything was working with the installed v11 ADS dll's. When I put the executable in directory with v9.10 dll's for advantage then any query that has an order by clause gets a 5116 error (advantage could not find an index order with the specified key expression). I am switching to FireDAC precisely to be able to use v9.10 of ADS to remain backwards compatible. I'm using XE4. |
|
collation mismatch? Did you reindex after changing the ACE? |
|
Hi all, I'm refloating this question as there is no specific answer and I'm having the same problem. I'm using XE5 Enterprise with Firedac against ADS V8. My problem comes out when I try to query over any table on my DD with an "order by" option, but not always happen, the tables I've tried with have a field char(30) which I want to order by. If I order by another field like integer works fine or even I dont use any order, the query runs fine too. Is this a problem with FD and my ADS V8 ?? Could be solved with XE6 or XE7 ? Does FD get better on those versions ? Thanks. |
FYI - Version 10.10 DLLs seem to work fine.
Unfortunately, I'm not that familiar with the inner-workings of FireDAC. Does FireDAC provide any logging that may be useful for gathering more information? I'm interested, specifically, in what key expression produces this error (and how that relates to the fields in the ORDER BY clause). Also, are there any errors logged in your Advantage error log that may shed a little more light on it?