UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
> Inherit Value List Property in 2007    
 
   
BGAccess
post Jul 24 2007, 05:27 PM
Post #1

UtterAccess Guru
Posts: 673
From: Northwest Ohio



Can someone explain to me what this means? I looked it up in the Access help but all that it says is the following:

Gets or sets whether a combo box's value list is inherited from its field. Read/write Boolean.

Isn't this just stating that the recordsource is the table or query that you set it to? I know, this is probably a stupid question, but I just don't understand it.
Go to the top of the page
 
+
GroverParkGeorge
post Jul 24 2007, 05:31 PM
Post #2

UA Admin
Posts: 22,032
From: Newcastle, WA



Is this refering to a multi-valued field, by any chance?


--------------------
Go to the top of the page
 
+
BGAccess
post Jul 24 2007, 05:56 PM
Post #3

UtterAccess Guru
Posts: 673
From: Northwest Ohio



Sorry... yes, it is a property for a combo box or a list box. I've changed it from No to Yes and back but I can't tell any difference in anything. According to the help section 2007 is the first version of Access it's been in.
Go to the top of the page
 
+
jmcwk
post Jul 24 2007, 06:10 PM
Post #4

UtterAccess VIP
Posts: 12,397
From: Tacoma, WA.



As George Suggests I think you are feferring to a Multi Value Field that was introduced in Access 2007 whereas it allows you to populate a Field with Multiple Values rather than being limited to 1 from the Same record Source. For example you wanted to know what Automobiles have I owned in the past 5 years the Multi Value Field (A Lookup) will allow you to list Ford, Chevrolet,Dodge in 1 record. Prior Versions would use 3 does that help any ??

The Multivalue Field is created at the Table Level Using a Lookup Table and the Wizard will walk you through it.


--------------------
John


Sharing Knowledge AND Working Together Yields Great Results!!! :)
Go to the top of the page
 
+
freakazeud
post Jul 24 2007, 06:15 PM
Post #5

UtterAccess VIP
Posts: 31,413
From: NC, USA



Hi,
it tells the combo/listbox if its value list comes from the lookup field it is bound to. Meaning that if you set the rowsource type property to value list and bound the control to a lookup field then setting the property ensures that the control inherits the value list values from the field.
Lookup fields are in general a bad idea. Read here for more.
HTH
Good luck


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

http://www.access-freak.com
Go to the top of the page
 
+
jmcwk
post Jul 24 2007, 06:17 PM
Post #6

UtterAccess VIP
Posts: 12,397
From: Tacoma, WA.



Oli,

Does that apply to 07 as well regarding A Multi Value Field ? I knew about prior Versions but.....

Thank You


--------------------
John


Sharing Knowledge AND Working Together Yields Great Results!!! :)
Go to the top of the page
 
+
freakazeud
post Jul 24 2007, 06:22 PM
Post #7

UtterAccess VIP
Posts: 31,413
From: NC, USA



The majority of people I talked to did not agree with the introduction. It somewhat goes against normalization rules to store multiple values in one field, right?


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

http://www.access-freak.com
Go to the top of the page
 
+
jmcwk
post Jul 24 2007, 06:29 PM
Post #8

UtterAccess VIP
Posts: 12,397
From: Tacoma, WA.



Agree 100% I am not a user of it or a fan as far as that goes of the Multi Value Field was just curious I guess why they would introduce it knowing the Rules as they are accepted by the Majority. Would the Attachment Field fall into the same General theory ? There are Multiple Attachments although it is not a Lookup


--------------------
John


Sharing Knowledge AND Working Together Yields Great Results!!! :)
Go to the top of the page
 
+
freakazeud
post Jul 24 2007, 06:40 PM
Post #9

UtterAccess VIP
Posts: 31,413
From: NC, USA



Yes...it has multiple values for one field. Many people wonder why MS has introduced the type even with feedback from many MVPs.


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

http://www.access-freak.com
Go to the top of the page
 
+
jurotek
post Jul 24 2007, 06:52 PM
Post #10

UtterAccess VIP
Posts: 1,420
From: NV



Multi-value field lookups data type was introduced to make it easier on novice to handle the pain with M:M.
I can envision problems when running SQL against non atomic value tho. I have 07 since last Nov here at the college and never used multi-value field lookups yet so I can't explore on that much further.
Attachment data was added to align better with Microsoft Windows SharePoint Services.


--------------------
"Perplexity is the beginning of knowledge". Kahlil Gibran
Go to the top of the page
 
+
jmcwk
post Jul 24 2007, 06:54 PM
Post #11

UtterAccess VIP
Posts: 12,397
From: Tacoma, WA.



Oliver, Jurotek Thanks for the input

Kevin, Sorry to somewhat get off your subject at hand


--------------------
John


Sharing Knowledge AND Working Together Yields Great Results!!! :)
Go to the top of the page
 
+
lgweaver
post Feb 11 2013, 12:08 PM
Post #12

New Member
Posts: 1



ok so look up fileds are bad... how do i get their utility without using them?
Go to the top of the page
 
+

Thank you for your support! Reply to this topicStart new topic

Jump To Forum:
 



RSS Search  ·  Go to Top  ·  Lo-Fi Version Time is now: 24th July 2014 - 07:24 AM