Board index » delphi » Field not found

2004-07-02 12:08:52 AM
delphi39
I had a simple locate that worked. I then applied some code to
force the window to the front as elegantly created by John
Herbert in this NG. Applied as follows:
fmCoreStart.ForceForegroundWindowOK (fmArchiveData.Handle);
if not Temp.Locate('JobNo',
archiveDM.Jobs.FieldByName('JobNo').Value, []) then begin
Code for forceforegroundwindowOK is included below. It does
indeed bring the window to the fore but it also breaks the
locate, for some reason giving an error 'Jobs Field JobNo not
found' but commenting out the call to
fmCoreStart.ForceForegroundWindowOK renders it functional
again.
Debug tooltip shows that JobsJobNo does actually exist. fwiw the
table has no fields defined at designtime.
function TfmCoreStart.ForceForegroundWindowOK (h: HWND):
boolean;
var hCurWnd: THandle;
begin
hCurWnd := GetForegroundWindow;
AttachThreadInput(
GetWindowThreadProcessId(hCurWnd, nil),
GetCurrentThreadId, True);
Result := SetForegroundWindow(h);
AttachThreadInput(
GetWindowThreadProcessId(hCurWnd, nil),
GetCurrentThreadId, False);
end;
Pat Bell
 

"P.S.Bell" <XXXX@XXXXX.COM>wrote
See tinyurl.com/ywu4c short for
www.google.com/groups
this a method?
This "form" is not a TDataModule is it?
I do not immediately see the problem. Maybe someone else
can help. Regards, JohnH
 

exposed myself a a rank amateur? :-)
 

a module with other utility code and one for doing
what you did:
(1) It requires copying and pasting of code for
each project that you use it in -- with the associated
chance for errors.
(2) It *implies* an untrue dependence of that code on
other things in the object. And that complicates the
view of the maintenance programmer.
(3) It does help to keep the form's code together.
(4) It makes it more difficult to reuse the code on
other projects.
Regards, JohnH
 

limelect writes:
Are the column names case sensitive in the database you are using?
Which ADO component are you using?
Is the ParamCheck property of your dataset component true?
If you instantiate field objects at design time do you see ApptID?
--
Bill Todd (TeamB)
 

Well it is fixed but i do not understand
1. the db is mdb
2. i added GroupAppt.ApptID
Manager1.RequestAppt(FieldByName(' GroupAppt.ApptID').AsString
and it is ok but why? in the bde db you did not need it?
the component is TAdoQuery thankes
"Bill Todd" <XXXX@XXXXX.COM>writes

limelect writes:
Is your SELECT a join on two tables that both contain ApptID?
Bill Todd (TeamB)