Alright

I am just about to start development on a new app and could do with a
bit of help I've got two ideas and just wondering which people
think is the best or quickest.

1:
I have a table (2 columns), it is used as a "lookup" table i.e.
Item Code
crisps 1
coke 2

etc...

My main table which stores my data has a field called "ItemCode" which
holds the code. I want to have a combobox that shows the "Item" field
from the lookup table but is bound to Item in my other table.

2:
combo box shows fields but isnt bound and then when the save button is
pressed an sql statement is executed which updates the row with the
new value. I think this method maybe slower when moving records
because ill have to set the values of all controls where as with
method 1 they will be bound.

Thanks

Chris

Use #2. IMHO binding has always been a waste of resources.

-Chris


"Chris" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Alright
>
> I am just about to start development on a new app and could do with a
> bit of help I've got two ideas and just wondering which people
> think is the best or quickest.
>
> 1:
> I have a table (2 columns), it is used as a "lookup" table i.e.
> Item Code
> crisps 1
> coke 2
>
> etc...
>
> My main table which stores my data has a field called "ItemCode" which
> holds the code. I want to have a combobox that shows the "Item" field
> from the lookup table but is bound to Item in my other table.
>
> 2:
> combo box shows fields but isnt bound and then when the save button is
> pressed an sql statement is executed which updates the row with the
> new value. I think this method maybe slower when moving records
> because ill have to set the values of all controls where as with
> method 1 they will be bound.
>
> Thanks
>
> Chris