When you are using data-aware controls directly connected to a database, what locks are issued on the table are dependent on the database and the driver you are using. You used to be able to avoid these using cached updates. The current recommended option is to use client datasets. Client datasets are in memory tables which get loaded with data from your database. The data-aware controls work against the client dataset allowing you to edit and update without affecting the actual database tables. Once you have finished you call the applyupdates method on the client dataset to store the modifications to the database. Hope that helps. Cheers, Anthony -----Original Message----- From: vdug-bounce@xxxxxxxxxxxxx [mailto:vdug-bounce@xxxxxxxxxxxxx]On Behalf Of Vivienne Awford Sent: Thursday, August 22, 2002 11:40 PM To: vdug@xxxxxxxxxxxxx Subject: [vdug] Bound controls or not? Is this still an issue? In the old days, bound controls were thought to cause problems by issuing table-level locks instead of row-level locks, and there is (was) added ?flexibility? with unbound controls. But have RDBMSs, and Delphi itself moved on enough for performance considerations to take a real back-seat such that unbound controls are just a productivity nightmare? Look forward to your feedback?. Vivienne