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 / Forms / May 2008

Tip: Looking for answers? Try searching our database.

Use one field to automatically determine data in another field

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
benbanyas - 15 May 2008 13:08 GMT
I'm sorry if this is confusing, but I am relatively new to Access and I can't
figure this out through Help.

I'm creating a museum database with data entered through a form. The
pertinent information for this question are fields "Collections", "Date
Entered", "Session #", and "Item #". Each entry can be from only 1
collection. Each collection can only have 1 session per day, but does won't
have one every day. Each Item # is dependent on the session (i.e. Item# 6
from Session 2). There are duplicates of every field because every collection
has multiple entries, there are multiple entries each day, the Session #s
begin at 1 for each Collection and the Item #s begin at 1 for each Session.

What I need it to do is see what Collection it is, then: If the most recent
Session was from the current date, Session # stays the same and Item # is
plus 1. If the most recent session was not the current date, Session # is
plus 1 and Item# is 1. Then I need these results to automatically be entered
and stored through the form. Is this possible?

I've tried queries, filters and tried to under stand the Iif and Lookup
functions and I am lost.
Thanks for any help in advance.
-Ben Banyas
scubadiver - 15 May 2008 13:19 GMT
There is no need for duplicates or multiple entries. Are you sure your
tables are properly normalised? Each table should contain unique information.

> I'm sorry if this is confusing, but I am relatively new to Access and I can't
> figure this out through Help.
[quoted text clipped - 18 lines]
> Thanks for any help in advance.
> -Ben Banyas
Jeff Boyce - 15 May 2008 13:42 GMT
As scubadiver's response indicates, there's rarely a need to duplicate data
in rows in a well-normalized relational database.  If these terms
("relational", "normalized") aren't familiar, you probably have a bit of a
learning curve before you can make good use of the features/functions Access
offers.

Consider posting a description of your table structure to the tablesdbdesign
newsgroup for feedback on how to normalize your data.

Signature

Regards

Jeff Boyce
www.InformationFutures.net

Microsoft Office/Access MVP
http://mvp.support.microsoft.com/

Microsoft IT Academy Program Mentor
http://microsoftitacademy.com/

> I'm sorry if this is confusing, but I am relatively new to Access and I can't
> figure this out through Help.
[quoted text clipped - 18 lines]
> Thanks for any help in advance.
> -Ben Banyas
 
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.