Re: SQL server Vs Oracle

From: Doug Hutcheson <Doug.Hutcheson_at_dnr.qld.gov.au.no.ham.spam.thank.you.mam>
Date: Fri, 14 May 1999 14:54:56 +1000
Message-ID: <7hgab8$fjs1@inet6.citec.com.au>

Ummm...

Pardon my ignorance, but exactly why do you want to use a combo box if you also want to disable it's combo features? A list box is what you want for that instance. A combo box is DESIGNED and thus INTENDED to allow entry of data other than that in the drop-down list - that's why it is called a combo box. Thus, arguing that data entry in a combo box is a flaw smacks rather heavily of a spurious argument.

But then, who am I to judge? Just a professional Access developer since Access 2, VB developer since VB 3, C programmer since year dot, VC++ developer since VC++1.5....etc, etc. Funny, the GUI tools all use the Windows combo box the same way - it is designed to let you type into the text area, so all the tools allow you to type into the text area.

You have some interesting arguments, but your credibility flies out the window when you advance a designed feature as a fault.

... or am I still missing something?

Hmmm....

--
Having fun with Access...
but then, I'm on medication...

Dev Ashish's site & FAQ: http://home.att.net/~dashish Microsoft support: http://support.microsoft.com/support News archive: www.dejanews.com.

The surest sign for the existence of intelligent life in the universe is that we have not been contacted.

Jim McCusker wrote in message <3739D949.29B3DC72_at_iname.com>...
>Abbot Cooper wrote:
>>
>> Jim McCusker wrote in message <3739B5F3.CBE02619_at_iname.com>...
>>
>> <SNIP>
>>
>> >I don't know, I didn't work on it. I do know that the two places I've
>> >worked (Pratt & Whittney and Xerox) there seemed to always be trouble
>> >with the exchange servers. My main point was, however, that the
>> >technology that Microsoft puts out tends to be unpredictable, whether it
>> >be from bugs or poor design decisions. For instance, try to get a native
>> >MS-Access combo-box to not be editable (only being able to select items
>> >from the pull-down). It's not gonna happen. But you can do this with VB
>> >and VC++. Why?
>>
>> Because you obviously don't know much about Access... I'm not trying to
>
>I've been working on it (professionally and not) since 2.0 came out. I'd
>say I know a bit about it.
>
>> stomp on you, but you are just making yourself look foolish with comments
>> like this. Access has a LimitToList property for combo-boxes, a property
of
>> which you are apparently not aware. If you set it to "Yes" then you will
not
>> be able to enter anything other than what is in the list. It works and to
>> the best of my knowledge always has worked just as it was intended to.
>
>See my previous post. You can still type in the box, which is what I
>didn't want to happen.
>
>Jim
>--
> Jim McCusker | Class of '99, BA Computer Science & Cognitive Science
> jc012e@uhura.cc.rochester.edu | http://cif.rochester.edu/~fprefect
> ~Those who do not understand Unix are condemned to reinvent it,
>poorly.~
> ~~Henry
>Spencer
Received on Thu May 13 1999 - 23:54:56 CDT