Re: ADOTable.Locate Workaround?
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 02/28/04
- Next message: Brian Bushay TeamB: "Re: Transforming Exception Errors into Friendly Messages"
- Previous message: Brian Bushay TeamB: "Re: Blob Data"
- In reply to: Chris LeFebvre: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Feb 2004 20:36:53 -0600
> For example, the table RegInfo has an numeric field called ID and
>using this hard coded locate:
> RegInfo.First;
> RegInfo.Locate('ID', VarArrayOf([104]), []);
>the locate returns false (no matching records) when I know for a fact
>that there's a record with an ID number of 104. Before I start making
>major changes I'd rather see if this can be made to work, any idea's?
User VarArrayOf only where there are multiple fields in the locate
Use this form for single field locate
RegInfo.Locate('ID', 104), []);
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Next message: Brian Bushay TeamB: "Re: Transforming Exception Errors into Friendly Messages"
- Previous message: Brian Bushay TeamB: "Re: Blob Data"
- In reply to: Chris LeFebvre: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]