LiveOak Posted January 3, 2001 Posted January 3, 2001 This would be done by creating a "compound key" upon which to base the relationship. For instance, in a timecard database is would be fairly inconvient to have a separate file for each employee's timecard records. With a simple key, each entry might be a date. With a compound key, each entry in the timecard file could be based upon an employee ID and a date. For instance: CmpdKey (calculation, text) = Right("0000" & EmpID, 4) & Date The perferred solutions is to use one file. For example, with four separate sections a report needing data from all four would be very difficult to create. -bd
[email protected] Posted January 4, 2001 Posted January 4, 2001 I have a project database with a layout for budgeting. The budget right now is broken into four general sections. Each of these sections has its own portal to an individual database that stores line items. I don't know if I need to have four seperate databases, though. Is there a way that I can make a relationship dependant on two sets of fields (project number and budget group) and keep all items in one database? Thanks for your help.
Recommended Posts
This topic is 8977 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now