Re: "unique table" problem
- From: "Keith G Hicks" <krh@xxxxxxxxxxx>
- Date: Wed, 29 Jun 2005 10:24:41 -0400
Thanks Brian. I'll move it.
"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
news:sd14c15dh8i27jje2mr42mhqk428fc5lii@xxxxxxxxxx
>2 other questions:
>
>1. Last night I ended up setting the UniqueTable in the AfterScroll event
of
>the TAdoDataset and it seems to work just fine. Does anyone see any
problem
>with that?
I believe that the Unique Table property is re-set to its null default after
a
ReQuery which is what the master detail link does.
I would set the property in the Beforedelete. AfterScroll has some overhead
if
you don't need it don't use it.
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.
- References:
- "unique table" problem
- From: Keith G Hicks
- Re: "unique table" problem
- From: Viatcheslav V. Vassiliev
- Re: "unique table" problem
- From: Keith G Hicks
- Re: "unique table" problem
- From: Brian Bushay TeamB
- "unique table" problem
- Prev by Date: Re: Parameter object is improperly defined. Access vs MSSQL
- Next by Date: Re: Update and insert in one sql statement in access error
- Previous by thread: Re: "unique table" problem
- Next by thread: Windows has no MS Access installed
- Index(es):
Relevant Pages
|
