Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / General 2 / June 2007

Tip: Looking for answers? Try searching our database.

Automatic transfer of data?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Milind - 29 Jun 2007 11:28 GMT
I have two tables, contacts & billing. In billing, I have Name & CustID
linked thru Lookups. I thought when CustID is chosen as 3, the corresponding
value for Name should appear on its own. Am I wrong or is there any other way
of doing it? Thanks
Scott McDaniel - 29 Jun 2007 12:00 GMT
>I have two tables, contacts & billing. In billing, I have Name & CustID
>linked thru Lookups. I thought when CustID is chosen as 3, the corresponding
>value for Name should appear on its own. Am I wrong or is there any other way
>of doing it? Thanks

If you mean you have a Lookup field defined on a table column, then stop right there and remove it - it's a bad, bad
design practice, since users should NEVER see your tables directly. The only positive thing about a lookup field is it
saves about10 seconds when adding a combo to your form.

http://www.mvps.org/access/lookupfields.htm

http://www.mvps.org/access/tencommandments.htm

That said, if you insist on using lookups, then you'd need to adjust the .ColumnWidths to show the correct value ... for
example, if your SQL is this:

SELECT CustID, CustName FROM tCustomers

And you did NOT set .ColumnWidths, the combo would show the CustID (the first field) ... if you set your .ColumnWidths
to 0;1, then Access will show the Name (since the first column width is set to 0).

But please - do away with the lookup fields, as they will come back to bite you (and usually sooner than later).

Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com
PFC Sadr - 29 Jun 2007 20:43 GMT
I disagree

I use lookup fields ALL THE TIME
and I don't think that your conclusions are correct or on the right
track.

Just because Access is too limited to use tools like Query Analyzer
(that don't use the lookups) it doesn't mean that they're not the best
thing since sliced bread.

I mean get real kids.

I use lookups everywhere-- and if I want to examine a table without
lookups; i'll use query analyzer
the answer is called 'Access Data Projects' in case you kids haven't
caught on yet

On Jun 29, 4:00 am, Scott McDaniel <scott@NoSpam_Infotrakker.com>
wrote:
> >I have two tables, contacts & billing. In billing, I have Name & CustID
> >linked thru Lookups. I thought when CustID is chosen as 3, the corresponding
[quoted text clipped - 21 lines]
> Scott McDaniel
> scott@takemeout_infotrakker.comwww.infotrakker.com
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.