That couldn't be easier! Much easier to tie it to a query then to take
everything out of a Excel ComboBox and then add it back in through a
recordset after every possible refresh.
As for the multi-select, I have normalized the database, but I don't want
the user to know about it. So I want them to be able to do something like
assign multiple authors to the same book in one action. So they see all
available authors as they're adding a new book. They can choose to put
attach two of them to the book they are adding (and it will update their
bridge table as well -- I can handle that SQL, just wondering about the
controls).
Thanks!
Klatuu said:
You can use a combo box to allow users to select from existing values in a
field.
You do that with a combo box. Set the combo's row source to a query that
gets unique values in the field with a query:
SELECT DISTINCT [SomeField] FROM SomeTable;
This will give you a list of one occurance of each value currently found in
the field.
Can you give more details about your multiselect question?
--
Dave Hargis, Microsoft Access MVP
mcleester said:
Thanks for the suggestion. What are the advantages of using Access (so I can
try to implement them)? Is there a good form to use to let users choose from
existing values from a field (and also multiple select)?
:
If the Excel UI is using an Access database, you will need Access installed
or the Access Runtime.
I would suggest you use Access. If you can write Excel macros using VBA,
the transition to Access wont be that hard.
--
Dave Hargis, Microsoft Access MVP
:
I have set up a database in access. I am now trying to make a decision about
how to make the user interface to it. My choices are between doing it in
Excel and doing it in Access. I am more comfortable in Excel, but I am
wondering if there are benefits to doing the VBA/forms in Access.
I am also wondering if I create the UI in Excel, can someone without Access
on their machine then use it? Because that would be a benefit for using
Excel. Any guidance is appreciated.