RE: Drop down list in form

Hi Everyone,
 
In noticed this thread and thought I would suggest an RFE. I am happy to
raise one if others agree.
 
I largely develop in MS Access. The functionality where if I enter a value
into a single column list box/combo box is the type of feature that I would
have liked available in MS Access a couple of times.
 
It appears that others would like this functionality too.
 
I think it would be good to have a property on the list box/combo box to the
effect "if not in list add to table" so the user can quickly add and use
this feature in their forms. 
 
IMHO if users don't have to write code then more users can use the product.
This type of feature could help separate Base from the pack. Add a whole
bunch of these type of ease of use features and Base becomes more valuable.
 
What do others think?
 
 
Regards,

Kelvin Eldridge
Online Connections
Website: www.onlineconnections.com.au <http://www.onlineconnections.com.au/>


Every day we solve and document clients problems.
We now have over 1,200 documented solutions.
Save time and money by checking the MyAnswers service.
Your problem may have already been solved.
www.onlineconnections.com.au/myanswers

 


  _____  

From: Andrew Jensen [mailto:[email protected]] 
Sent: Friday, 12 August 2005 4:44 AM
To: [email protected]
Subject: Re: [dba-users] Drop down list in form


Mark,

It would be nice and the nice thing about a community open source project is
you can always request it as a
new feature in a future release.

Also, thanks for the 'well done' but the macro isn't really that good. It
was just a down an dirty example. Two big problems
first you would have to hand write a new sub procedure for every new control
you wanted to do this to. Second
the way I am calling it would die as soon as an actual Foriegn Key was
created at the table level.

Neither problem is too hard to fix. For the first I suppose one would
refactor it thusly. Create 
a work macro that takes as parameters the table name, column name and value
to check for. Then
call this work macro from a event handler macro for the specific control or
form that gets the specific
parameters. As for the logic flow, it needs to be called before the primary
record is posted, not aftter
so that the value can be in the Foriegn key table.

I am planning to rewrite for thiese issues and when I do I will post it at
the OooForum CodeSnippet board
and post a message here with the message number.

Andrew

Marc Santhoff wrote: 

Am Donnerstag, den 11.08.2005, 13:35 -0400 schrieb Andrew Jensen:

  

Marc Santhoff wrote:

    

[...]

  

mark,



Look back a couple of messages the sample macro I posted does just that. 

Puts new values into the table that supplies the list values. I combo 

box is used so that this new

value can be entered. No button is needed.

    



Well done, i overklooked that one. But I agree with the fact that it

would be at least "nice to have" if the combobox itself could be used in

this manner.



Thanks,

Marc







---------------------------------------------------------------------

To unsubscribe, e-mail: [email protected]

For additional commands, e-mail: [email protected]