A truly humongously stupid question, I am sure, but I am curious as to
how you access your one-byte fields?

I have tried to use AsString, but it returns empty. AsInteger, the
obvious choice, gives me "cannot access field as type integer."

I'm sure there is a really really simple solution, so I'm looking
forward to the answer. Cheers!

Dominique,
  How did you put the data into the byte fields?

Barry

Dominique Willems wrote:

> A truly humongously stupid question, I am sure, but I am curious as to
> how you access your one-byte fields?
>
> I have tried to use AsString, but it returns empty. AsInteger, the
> obvious choice, gives me "cannot access field as type integer."
>
> I'm sure there is a really really simple solution, so I'm looking
> forward to the answer. Cheers!

Hmm, I don't have such types but have you tried .AsBytes ?

Dominique


What datatype are you using to create the column in the table? One problem will probably be that some types either don't match well to their potential Delphi equivalent of just don't match.

I just created a 1 Byte column - what you have to do is

procedure TForm1.Button1Click(Sender: TObject);
var
xx:string;
yy:integer;
begin
xx:=test.fieldbyname('_bytes').asstring;
yy:=ord(xx[1]);
showmessage(inttostr(yy));
end;


In my case I'd shoved 05 into it in EDBManager

Roy Lambert

Barry wrote:
> Dominique,
>    How did you put the data into the byte fields?

..AsString.

And to read it:
Ord(tbTestByte.AsString[1])

but it was returning empty strings. So I gave up and am now just using
SmallInt fields. Bit of a waste, but more elegant. If only a byte field
were accessible through AsInteger.

Malcolm wrote:
> Hmm, I don't have such types but have you tried .AsBytes ?

I have. Unsuccessfully.

Roy Lambert wrote:
> xx:=test.fieldbyname('_bytes').asstring;
> yy:=ord(xx[1]);

I got access violations because the string was empty, while the field
never was. Odd, but I eventually gave up and reverted to SmallInt
fields.

Dominique


Was it unicode or ansi? I tested using ansi cos that's what I use.

Roy Lambert [Team Elevate]

Roy Lambert wrote:
> Was it unicode or ansi? I tested using ansi cos that's what I use.

Unicode.

Dominique


<WARNING>

Everything that follows is a guess because I'm still running D2006.

</WARNING>

In that case you may be hitting the ansi/unicode problem. field.AsString will return a unicode string, Ord I assume has be altered to handle this but you're passing it a single byte and its throwing a wobbly.

There may be a specific version for ansichar or you may have to explicity cast your data to ansichar to trigger overloading in the standard version.

Roy Lambert [Team Elevate]