ADOTable.Locate Workaround?
From: Chris LeFebvre (LeFebvreC_at_Comcast.Net)
Date: 02/25/04
- Next message: Eric ten Westenend: "CommandText does not return a result set with select statement!"
- Previous message: Brian Bushay TeamB: "Re: Access & Transactions"
- Next in thread: Eric ten Westenend: "Re: ADOTable.Locate Workaround?"
- Reply: Eric ten Westenend: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 24 Feb 2004 22:37:16 -0500
I'm currently working on a front end (Delphi 6, SP2) for an Access
2000 database (not my choice of databases but that's what the client
wants) I'm using ADOConnection, ADOTable, ADOQuery components and then
the standard datasource and various data aware controls. The front end
really works fine and the customer likes it a lot but I'm having a
problem getting a Find function working and from various messages I see
in the forum here I gather that there's a bug of some type in the
adotable.locate function. There are several references to the
BetterAdoDataSet component as a solution to this problem but I'm not
using the AdoDataset component so I'm not sure how I could use it to
solve the problem? Are there any other alternatives for work arounds for
the locate bug?
Thanks,
- Chris LeFebvre
- Next message: Eric ten Westenend: "CommandText does not return a result set with select statement!"
- Previous message: Brian Bushay TeamB: "Re: Access & Transactions"
- Next in thread: Eric ten Westenend: "Re: ADOTable.Locate Workaround?"
- Reply: Eric ten Westenend: "Re: ADOTable.Locate Workaround?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|