I am trying to compile/build edbutilcompsdesign.dpk using XE2 (Unicode) but I get a compiler error:

[DCC Error] edbutilcomps.pas(1892): E2010 Incompatible types: 'PAnsiChar' and 'PWideChar'
[DCC Error] edbutilcomps.pas(1894): E2010 Incompatible types: 'PAnsiChar' and 'PWideChar'

     lpFile:=pEDBChar(FileName);                        //First error
     lpParameters:=nil;
     lpDirectory:=pEDBChar(DefaultDirectory);      //Second error


lpFile and lpDirectory are defined in Winapi.ShellAPI as PAnsiChar;

I'm not sure where pEDBChar is defined. I don't have the EDB source code for the server.
Any suggestions?

TIA

Barry
EDB V2.11 B2

Barry,

posted earlier by Tim:

<< When compiling the extra utils into a package with the edbutilcomps.pas
found in the UNICODE version I get the following errors: >>

You need to make sure that you compile the package with this directive:

EDB_UNICODE

That is the universal directive used in ElevateDB to tell a unit that you
are using the Unicode version.

Regards Uli

Uli,
>You need to make sure that you compile the package with this directive:
EDB_UNICODE
That is the universal directive used in ElevateDB to tell a unit that you
are using the Unicode version.<

Thanks, that worked. I thought this would be mentioned in an .inc file or at the top of the .PAS file, but it wasn't. Where would I look in the EDB documentation to find "EDB_Unicode" and other conditional variable?

Barry

Barry,

> Where would I look in the EDB documentation to find "EDB_Unicode" and other conditional variable?

I have no idea. Maybe it's not documented at all. I searched the
pdf-files and couldn't find anything containing "EDB_Unicode".

Uli

Barry,

<< Thanks, that worked. I thought this would be mentioned in an .inc file or
at the top of the .PAS file, but it wasn't. Where would I look in the EDB
documentation to find "EDB_Unicode" and other conditional variable? >>

It's not really mentioned anywhere - we only have a few customers that
re-compile the EDB design-time/utils code  so it hasn't been a high priority
in terms of documentation.

I'll see about adding a mention in the manual.

Tim Young
Elevate Software
www.elevatesoft.com