A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » New Users
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

"The dreaded lookup field"



 
 
Thread Tools Display Modes
  #1  
Old April 28th, 2007, 05:58 PM posted to microsoft.public.access.gettingstarted
Sue[_2_]
external usenet poster
 
Posts: 47
Default "The dreaded lookup field"

So when is it OK to use one? Must I banish combo boxes to outer darkness?


  #2  
Old April 28th, 2007, 06:54 PM posted to microsoft.public.access.gettingstarted
Ken Snell \(MVP\)
external usenet poster
 
Posts: 2,506
Default "The dreaded lookup field"

A misunderstanding, I think. Combo boxes are very good and useful and are
not to be banned. Plus they greatly facilitate the elimination of people
entering bad data.

The "lookup" field issue relates to the property that you can set for a
field in the table itself. Don't do that! Leads to problem when you look at
data that it appears to be the lookup value but instead is the real value;
people forget that and wonder why their queries don't work when they try to
find records where that field's value is the looked-up value and not the
real value.
--

Ken Snell
MS ACCESS MVP

"Sue" wrote in message
...
So when is it OK to use one? Must I banish combo boxes to outer darkness?



  #3  
Old April 28th, 2007, 07:03 PM posted to microsoft.public.access.gettingstarted
Sue[_2_]
external usenet poster
 
Posts: 47
Default "The dreaded lookup field"

Thanks for clarifying.


"Ken Snell (MVP)" wrote in message
...
A misunderstanding, I think. Combo boxes are very good and useful and are
not to be banned. Plus they greatly facilitate the elimination of people
entering bad data.

The "lookup" field issue relates to the property that you can set for a
field in the table itself. Don't do that! Leads to problem when you look
at data that it appears to be the lookup value but instead is the real
value; people forget that and wonder why their queries don't work when
they try to find records where that field's value is the looked-up value
and not the real value.
--

Ken Snell
MS ACCESS MVP

"Sue" wrote in message
...
So when is it OK to use one? Must I banish combo boxes to outer darkness?





  #4  
Old April 29th, 2007, 01:16 AM posted to microsoft.public.access.gettingstarted
John W. Vinson
external usenet poster
 
Posts: 18,261
Default "The dreaded lookup field"

On Sat, 28 Apr 2007 13:54:28 -0400, "Ken Snell \(MVP\)"
wrote:

A misunderstanding, I think. Combo boxes are very good and useful and are
not to be banned. Plus they greatly facilitate the elimination of people
entering bad data.


Well... they don't eliminate the *people*. You have to call the HR department
(or Cousin Luigi) to do that!

g, d & r

John W. Vinson [MVP]
  #5  
Old April 29th, 2007, 01:46 AM posted to microsoft.public.access.gettingstarted
Ken Snell \(MVP\)
external usenet poster
 
Posts: 2,506
Default "The dreaded lookup field"

"John W. Vinson" wrote in message
...
On Sat, 28 Apr 2007 13:54:28 -0400, "Ken Snell \(MVP\)"
wrote:

A misunderstanding, I think. Combo boxes are very good and useful and are
not to be banned. Plus they greatly facilitate the elimination of people
entering bad data.


Well... they don't eliminate the *people*. You have to call the HR
department
(or Cousin Luigi) to do that!


Yep, you're right... a bit of "wishful thinking" crept into my reply.....
--

Ken Snell
MS ACCESS MVP


  #6  
Old April 29th, 2007, 05:03 PM posted to microsoft.public.access.gettingstarted
tina
external usenet poster
 
Posts: 1,997
Default "The dreaded lookup field"

hmm, do you think MS might add that option to the next version of Access?
i'd buy it in a heartbeat! bg


"Ken Snell (MVP)" wrote in message
...
"John W. Vinson" wrote in message
...
On Sat, 28 Apr 2007 13:54:28 -0400, "Ken Snell \(MVP\)"
wrote:

A misunderstanding, I think. Combo boxes are very good and useful and

are
not to be banned. Plus they greatly facilitate the elimination of people
entering bad data.


Well... they don't eliminate the *people*. You have to call the HR
department
(or Cousin Luigi) to do that!


Yep, you're right... a bit of "wishful thinking" crept into my reply.....
--

Ken Snell
MS ACCESS MVP




  #7  
Old April 30th, 2007, 02:21 AM posted to microsoft.public.access.gettingstarted
Ken Snell \(MVP\)
external usenet poster
 
Posts: 2,506
Default "The dreaded lookup field"

"tina" wrote in message
...
hmm, do you think MS might add that option to the next version of Access?
i'd buy it in a heartbeat! bg


I don't think it's on the "top 100" list right now..... s

--

Ken Snell
MS ACCESS MVP



  #8  
Old April 30th, 2007, 02:49 AM posted to microsoft.public.access.gettingstarted
Jeff Conrad [MSFT]
external usenet poster
 
Posts: 233
Default "The dreaded lookup field"

"tina" wrote in message:
...

hmm, do you think MS might add that option to the next version of Access?
i'd buy it in a heartbeat! bg


It's in the specs at the moment.....



I'm kidding, just kidding!!
:-)

--
Jeff Conrad - Access Junkie - MVP Alumni
Software Development Engineer in Test
XAS Services
Microsoft Corporation

Co-author - Microsoft Office Access 2007 Inside Out
Presenter - Microsoft Access 2007 Essentials
http://www.accessmvp.com/JConrad/accessjunkie.html
Access 2007 Info: http://www.AccessJunkie.com

----------
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.mspx
----------


  #9  
Old April 30th, 2007, 02:52 AM posted to microsoft.public.access.gettingstarted
John W. Vinson
external usenet poster
 
Posts: 18,261
Default "The dreaded lookup field"

On Sun, 29 Apr 2007 21:21:19 -0400, "Ken Snell \(MVP\)"
wrote:

"tina" wrote in message
...
hmm, do you think MS might add that option to the next version of Access?
i'd buy it in a heartbeat! bg


I don't think it's on the "top 100" list right now..... s


I think it's been on request since before there was a Microsoft... remember
the XOI instruction? Execute Operator Immediate...

John W. Vinson [MVP]
  #10  
Old April 30th, 2007, 03:49 AM posted to microsoft.public.access.gettingstarted
Tom Lake
external usenet poster
 
Posts: 193
Default "The dreaded lookup field"


"tina" wrote in message
...
hmm, do you think MS might add that option to the next version of Access?
i'd buy it in a heartbeat! bg


They had it in Alpha testing but it eliminated the entire team that was
doing the testing.
Now it's tough for MS to find people willing to work on it any further.

Tom Lake

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 05:31 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.