Troy said:
Thanks for the response. Essentially it is just a basic asset database, and
all I am wanting to do is associate a user against a specific
item/desktop/etc as the owner. So when someone leaves - in theory this device
will be updated to having the owner of the person who replaces them (or at
least fills their shoes as the owner/user of that device).
So to answer your question - do I need a list - yes I pretty much do, as I
want to select which user will be the owner.
Good enough. Yes, you do need a list.
Thanks for the advice on the vb stuff - I had figured that would have been
an option - however alas I am a virgin when it comes to code (asides from
t-sql), so all that seems daunting - but most likely by the sounds of things
necessary.
Oy, this is not simple stuff. You will need to work with call back
functions filling combo boxes. This is not for the faint-of-heart.
It takes me at least half an hour to an hour to get a call back
function filling a combo box working properly. And I've done this
before and have been programming for about 27 years.
Although, now that I think about it, you could use a temporary table
which you fill every time the user goes into the application and
reference that table as the source for the combo box. Yeah, that'd
work.
If you can offer any other feedback/detail/advice etc it would be much
appreciated....off to groups.google.com now

*might search for "crash
course in vb" too
When I get a moment I'll do some searching.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm