Results 1 to 5 of 5
  1. #1
    FormerJarHead is offline Advanced Beginner
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2012
    Posts
    52

    Front End / Back End Question

    Good day all,

    My db has a front end / back end for a multi user environment. In the BE, I have a table with a field using a combo box. I set the control source, (Table/Query), column widths (0;1.25), column count (2) and bound columns (1). All is good in the BE. When I look at the same table in the FE, all is the same except column count. It only shows (1) which is the TableID field. The data I really need to get to is contained in the second column. Can I force the FE to mirror the data design in the BE or should I make the BE column count (1) and remove the ID field?

    Thank you

  2. #2
    June7's Avatar
    June7 is online now VIP
    Windows 7 64bit Access 2010 32bit
    Join Date
    May 2011
    Location
    The Great Land
    Posts
    53,771
    Advise not to set lookups in table. http://access.mvps.org/access/lookupfields.htm

    Build combo and list boxes on forms.

    However, if the table lookup is set then dragging the field from field list when designing form/report should adopt those properties (which, by they way, are useless in report).

    Why don't you want the ID field? Is it not the primary key?
    How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.

  3. #3
    ssanfu is offline Master of Nothing
    Windows XP Access 2000
    Join Date
    Sep 2010
    Location
    Anchorage, Alaska, USA
    Posts
    9,664
    It sounds like you have a lookup FIELD in the BE.
    I NEVER use lookup fields. Note that a lookup TABLE (good) is different than a lookup FIELD (bad).

    See The Evils of Lookup Fields in Tables
    http://access.mvps.org/access/lookupfields.htm


    I set the control source (Table/Query), column widths (0;1.25)
    In the BE, try removing the column widths values or set the column widths to (1;1.25)

    Lookup fields in tables (IMO) are a waste of time. In a combo box on a form, you have to re-setup the same values as the lookup field. So you have spent double the time for no advantage. Plus, this "feature" is not supported in any other RDMS (SQL Server, Oracle, MySQL, DB2,....).

  4. #4
    orange's Avatar
    orange is offline Moderator
    Windows XP Access 2003
    Join Date
    Sep 2009
    Location
    Ottawa, Ontario, Canada; West Palm Beach FL
    Posts
    16,870
    Agree totally with June and Steve -- the field level table lookup and multivalued fields are a concoction from M$oft limited to Access. Most will tell you to avoid these constructs. Lookup tables, usually used with Forms and sometimes referred to as reference tables, have been around for a long time and have been and are used in other DBMSs.

  5. #5
    FormerJarHead is offline Advanced Beginner
    Windows 7 64bit Access 2010 64bit
    Join Date
    Oct 2012
    Posts
    52
    Thanks to all of you for your knowledge. I will make the changes...

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Front End vs. Back End
    By athyeh in forum Access
    Replies: 2
    Last Post: 07-08-2013, 01:28 PM
  2. Replies: 5
    Last Post: 05-27-2013, 09:34 AM
  3. linking the back end to the front end
    By mike02 in forum Access
    Replies: 4
    Last Post: 04-24-2013, 11:15 AM
  4. Front end link to back end
    By Melo in forum Security
    Replies: 4
    Last Post: 01-21-2011, 09:25 PM
  5. Different passwords on front-end & back-end?
    By Delta223 in forum Access
    Replies: 3
    Last Post: 01-07-2011, 09:25 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums