 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Robert
Guest
|
 Posted: Fri Dec 23, 2005 3:42 am Post subject: Design question - lookup |
 |
|
I have a transaction table, updated throughout the day by multiple
operators. There is also an operator table, which contains the operator code
(integer), name, password, and some more data.
I would like to add to the transaction table the operator code, and then
display the operator name. Via a lookup field added to the table, I guess.
The system is very tTable oriented so while I could use SQL, it would be a
significant change.
The problem is, the transaction table is used very heavily, and I don't want
for the lookup to be active all the time, just in the forms that display
transactions in a grid. Any other time, it should not be adding overhead to
the processing.
Any clever way of enabling/disabling a lookup?
Robert
|
|
| Back to top |
|
 |
Bill Todd
Guest
|
| Posted: Fri Dec 23, 2005 1:13 pm Post subject: Re: Design question - lookup |
|
|
To disable the lookup try setting the LookupDataSet property to nil. To
enable the lookup set the property to the DataSet component that
supplies the lookup data.
--
Bill Todd (TeamB)
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
