SupWang
asked on
Question about the "FieldByName"
Hi all,
Why this always return a Null value?
-------------------------- >
FieldByName('EventMessage' ).Value := FieldByName('EventMessage' ).Value + 'test';
-------------------------- <
Change to the following can get the correct result.
-------------------------- >
FieldByName('EventMessage' ).Value := FieldByName('EventMessage' ).AsString + 'test';
-------------------------- <
I also use "FieldByName('XXXXX').Valu e" in other place, Do I must change them to AsFloat/AsInteger/As..... ?
(Using D3)
Thanks, supwang
Why this always return a Null value?
--------------------------
FieldByName('EventMessage'
--------------------------
Change to the following can get the correct result.
--------------------------
FieldByName('EventMessage'
--------------------------
I also use "FieldByName('XXXXX').Valu
(Using D3)
Thanks, supwang
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SupWang I would suggest not even using Value becuase as Drareg mentioned Value is a TVariant and using variants can slow down the proccess because it takes proccessor time to convert the data to the type that it is. Try getting in the habit of using AsString, AsInteger, AsDateTime etc.
The Crazy One
The Crazy One
ASKER
Hi CrazyOne,
If it is a persistent field, Do I also need to change ".Value" to AsString, AsInteger, AsDateTime etc?
Regards, supwang
If it is a persistent field, Do I also need to change ".Value" to AsString, AsInteger, AsDateTime etc?
Regards, supwang
Yes, If you know the data type then it is best to use .AsString, .AsInteger, .AsDateTime. Experiment with this to get the overall feel of it. Example:
FieldByName('EventMessage' ).AsString := FieldByName('EventMessage' ).AsString + 'test';
One thing I do is to use a variable to capture the field's value. Mainly because I might need to use this value over and over again. Using the variable will cut down on the number of calls I need to make to the field which has the possible benefit of speeding up the process and shorting the length of the code making it easier to read. Again this something one needs to experiment with to see how it works for them.
var
s: string;
begin
s := FieldByName('EventMessage' ).AsString ;
FieldByName('EventMessage' ).AsString := s + 'test';
In this case the there is not much benefit in using the variable approach. But lets say we call on this field many times in our code then using the variable should improve performance. Example:
if s = 'a' then
DoSomething
else if s = 'b' then
DoSomething
else if s:= 'c' then
DoSomething
else if s = 'd' then
DoSomething
else if s = 'e' then
DoSomething
else if s = 'f' then
DoSomething
else if s = 'g' then
DoSomething
else if s = 'h' then
DoSomething;
Now a neat thing here is lets say we have label and we want to set the caption of this label to that of a field that is an integer type. We can do this rather easily by using the .AsString.
Example:
Label1.Caption := FieldByName('AnIntegerFiel d').AsStri ng;
This will convert the Integer field to a string for us.
The main point I am trying to make is no matter whether your code is dealing with values from a database or your code is manipulating or tracking values you create in the code try and stay away from using variants unless you absolutely need to. Variants definitely slow down the processing of the code.
FieldByName('EventMessage'
One thing I do is to use a variable to capture the field's value. Mainly because I might need to use this value over and over again. Using the variable will cut down on the number of calls I need to make to the field which has the possible benefit of speeding up the process and shorting the length of the code making it easier to read. Again this something one needs to experiment with to see how it works for them.
var
s: string;
begin
s := FieldByName('EventMessage'
FieldByName('EventMessage'
In this case the there is not much benefit in using the variable approach. But lets say we call on this field many times in our code then using the variable should improve performance. Example:
if s = 'a' then
DoSomething
else if s = 'b' then
DoSomething
else if s:= 'c' then
DoSomething
else if s = 'd' then
DoSomething
else if s = 'e' then
DoSomething
else if s = 'f' then
DoSomething
else if s = 'g' then
DoSomething
else if s = 'h' then
DoSomething;
Now a neat thing here is lets say we have label and we want to set the caption of this label to that of a field that is an integer type. We can do this rather easily by using the .AsString.
Example:
Label1.Caption := FieldByName('AnIntegerFiel
This will convert the Integer field to a string for us.
The main point I am trying to make is no matter whether your code is dealing with values from a database or your code is manipulating or tracking values you create in the code try and stay away from using variants unless you absolutely need to. Variants definitely slow down the processing of the code.
Hi SupWang,
yes, field property Value is variant type. Empty field Value = 'NULL'.
Concatenation of string and 'NULL' always = 'NULL'.
You can notice the same behavior after executing SQL statement which has some concatenation.
e.g.
select FirstName || LastName from TheTable
the result will be empty if one of fields is NULL.
btw assignin empty string to empty field convert result to empty string.
FieldByName('EventMessage' ).Value := '';
FieldByName('EventMessage' ).Value := FieldByName('EventMessage' ).Value + 'test';
should return valid result.
------
Igor.
yes, field property Value is variant type. Empty field Value = 'NULL'.
Concatenation of string and 'NULL' always = 'NULL'.
You can notice the same behavior after executing SQL statement which has some concatenation.
e.g.
select FirstName || LastName from TheTable
the result will be empty if one of fields is NULL.
btw assignin empty string to empty field convert result to empty string.
FieldByName('EventMessage'
FieldByName('EventMessage'
should return valid result.
------
Igor.
ASKER
Hi all,
How about the TTime field? Use "ThisTime.AsDateTime" instead of "ThisTime.Value"?
Regards, supwang
How about the TTime field? Use "ThisTime.AsDateTime" instead of "ThisTime.Value"?
Regards, supwang
AsDateTime, you can always convert it to the format you need when you actually need to use it.
ASKER
Hi all,
Thank you very much. I had already changed many many lines in my program.
Hi CrazyOne,
Have some points for you, Please go here: https://www.experts-exchange.com/jsp/qManageQuestion.jsp?ta=delphi&qid=20276807
Hi ITugay,
Have some points for you, Please go here:
https://www.experts-exchange.com/jsp/qManageQuestion.jsp?ta=delphi&qid=20276808
Best Regards, supwang
Thank you very much. I had already changed many many lines in my program.
Hi CrazyOne,
Have some points for you, Please go here: https://www.experts-exchange.com/jsp/qManageQuestion.jsp?ta=delphi&qid=20276807
Hi ITugay,
Have some points for you, Please go here:
https://www.experts-exchange.com/jsp/qManageQuestion.jsp?ta=delphi&qid=20276808
Best Regards, supwang
ASKER