Re: ADOTable.Locate Workaround?
From: Chris LeFebvre (LeFebvreC_at_Comcast.Net)
Date: 02/27/04
- Next message: Dave Blake: "Re: Access Table corrupts on one network machine"
- Previous message: Dave: "Re: Access Table corrupts on one network machine"
- In reply to: Brian Bushay TeamB: "Re: ADOTable.Locate Workaround?"
- Next in thread: Vassil Nazarov: "Re: ADOTable.Locate Workaround?"
- Reply: Vassil Nazarov: "Re: ADOTable.Locate Workaround?"
- Reply: Brian Bushay TeamB: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 27 Feb 2004 12:01:03 -0500
Hi Brian:
Thanks for the tips, but I do have an odd problem here.. you mention
that TAdoTable.Locate has problems when there's a filter applied and my
problem is that I'm not using any filters and locate consistently
doesn't find records that I know are there.
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?
Thanks,
- Chris LeFebvre
- Next message: Dave Blake: "Re: Access Table corrupts on one network machine"
- Previous message: Dave: "Re: Access Table corrupts on one network machine"
- In reply to: Brian Bushay TeamB: "Re: ADOTable.Locate Workaround?"
- Next in thread: Vassil Nazarov: "Re: ADOTable.Locate Workaround?"
- Reply: Vassil Nazarov: "Re: ADOTable.Locate Workaround?"
- Reply: Brian Bushay TeamB: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]