Odd LiteDAC problem in 64bit

Discussion of open issues, suggestions and bugs regarding LiteDAC (SQLite Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
Steven
Posts: 30
Joined: Fri 06 Dec 2013 19:48

Odd LiteDAC problem in 64bit

Post by Steven » Fri 06 Dec 2013 20:13

I'm evaluating the trail version of LiteDAC (v2.1.4) with Delphi Xe2.

In an earlier prototype of my app when I was just displaying the data in a DBGrid everything worked fine in both the 32 & 64 bit compiled versions.

Now that I'm adding extra data handling I'm having problems - but only in 64bit mode.
When running in 64bit trying to get the contents of some of the fields by name
i.e. n_ID := head_q.FieldByName('Cont_ID').Value;
(where head_q is a TLiteQuery object)
produces the error
ProjectTest1.exe raised exception EDatabaseError with message 'LiteQuery1: Field 'Cont_ID' not found'.

What's puzzling is that in 64 bit some fields get the error and others don't, yet all fields show in the DBGrid. When compiled as a 32bit exe everything works fine.

Code: Select all

var
  n_ID : Integer;
begin
  n_ID := head_q.FieldByName('Vendor_ID').Value;  //this works - Integer field
  n_ID := head_q.FieldByName('Cont_ID').Value;    //<<produces error in 64 bit!

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Odd LiteDAC problem in 64bit

Post by AlexP » Mon 09 Dec 2013 07:03

Hello,

Such behaviour (works only with 6 first fields) is a restriction of the trial versions of our products for non Win32 platforms.

Steven
Posts: 30
Joined: Fri 06 Dec 2013 19:48

Re: Odd LiteDAC problem in 64bit

Post by Steven » Mon 09 Dec 2013 07:28

Thanks, that clears things up.
I thought that limitation was only if you tried running app not in the IDE.

AlexP
Devart Team
Posts: 5530
Joined: Tue 10 Aug 2010 11:35

Re: Odd LiteDAC problem in 64bit

Post by AlexP » Mon 09 Dec 2013 09:49

Hello,

This restriction applies to both design-time and run-time independing on how the application is launched (from the IDE or via the exe file).

Post Reply