Forums
New posts
Search forums
Members
Current visitors
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Table Design
Constraint Clause on Relationships
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Reply to thread
Message
[QUOTE="Jeff Boyce, post: 2583878"] Kim From your description, it sounds like you have a table with a lookup-type data field. If you are aware of the confusion this data type can cause and have designed ways to insulate the user from those confusions, and have documentation for yourself (and for anyone else who might need to work "behind the curtain" on this application), then you probably don't need to consider changing the lookup data type to the underlying field data type. If you aren't certain on all of these, and if you/your successor/your users will be working directly in the tables, think twice about using the lookup data type (in the table) -- the alternative, to gain the advantage of lookups, is to use forms and combo or list boxes. Besides, Access tables are designed to store data, forms (and reports) to display it. Good luck! -- Regards Jeff Boyce [URL="http://www.InformationFutures.net"]www.InformationFutures.net[/URL] Microsoft Office/Access MVP Microsoft IT Academy Program Mentor [URL]http://microsoftitacademy.com/[/URL] [/QUOTE]
Verification
Post reply
Forums
Archive
Newsgroup Archive
Access Newsgroups
Access Table Design
Constraint Clause on Relationships
Top