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]




  

Reply via email to