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 1 / April 2006

Tip: Looking for answers? Try searching our database.

Archiving Records for Historical Tracking

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Lawdawg - 05 Apr 2006 18:29 GMT
I have been task with writing an Inventory Tracking program for my group and
ran into a small problem.  I have two numbers used in issuance of inventory
(1) and item number (2) a serial number both of these are set  for no
duplicates so the same item is not issued twice.  One number is set for one
office as they need an item number to track issued items and the another
office uses a serial number as they do the purchasing. My question is, how
can I create a history tracking file to track turn in items and re-issue
items with the same item number and serial number.  I also have a date issue
and a date return fields in the data base.  I have had a very basic
introduction to Access Class and this was not covered.  Thank you for your
time in advance for any assistance you can provide with this issue.
pietlinden@hotmail.com - 05 Apr 2006 21:08 GMT
If an item can be issued and returned multiple times, you can't use
just the itemID or whatever as primary key.  You need something like
{itemID, issueDate} or something like that as a compound primary key.
Make friends with the Access Help.  There's tons of stuff in there.
also poke through some of the sample databases.
Lawdawg - 06 Apr 2006 11:48 GMT
Thanks for your time and the information, I will look closer in the mentioned
items.

>If an item can be issued and returned multiple times, you can't use
>just the itemID or whatever as primary key.  You need something like
>{itemID, issueDate} or something like that as a compound primary key.
>Make friends with the Access Help.  There's tons of stuff in there.
>also poke through some of the sample databases.
 
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.