I have tbl_orders which records orders. I have a linked table called tbl_order_lines which details the items against each order.
In a nutshell, an item can only appear once in an order. However, I do not know how to create a relationship or code the frm_order in order to reflect this in my DB.
I have a couple of tables which only have a single field. Is it worth adding a second field in order to hold an ID number (is this commonly termed an index number?) for each entry.
My other tables with multiple fields include a field for an ID number and these tables are linked via these fields.
At this stage I cannot see any reason why, in the future, I would want to add additional fields to the tables which I am currently planning to make single field.
I am trying to create a one-to-many relationship between these two tables. I want to be able to access the 3 fields on the [Processors] table within reports based on [AllItems]. [AllItems] is a listing of account activity where the [AccountNumber] repeats. I have every field set as the "Primary Key" on [AllItems] as that is the only way to avoid importing duplicate data. I am getting the error: "no unique index found for the referenced field of the primary table"
View 3 Replies View RelatedI am attempting to build a table relationship, however when I enforce referential integrity, I keep receiving the message: "No unique index found for the referenced field of the primary table".
I checked and I have no duplicates in the primary table or secondary table.I will set up the two tables as thus: 1. Master table - People Who Eat 2. Secondary table - a table for all people who eat pizza.
I am trying to link my pizza table to the Poeple Who Eat table. I have created my own primary key for each table (an account number). My secondary table is much smaller in population than the People Who Eat table (which would include data from other subgroups). I am trying to get the 'yes'/'no'/'uncertain' from the secondary table into the primary table without manual entry.
I have searched all over the web and have not been able to find why the tables will not link. I am new to Access, so there may be something I am overlooking. Is there a way to get this information from the other table other than building a relationship?
I created a database a few years ago and it has been working well. This database is split.
Recently I started to update the front end based on user feedback and I am adding some queries.
I am noticing that sometimes I try to create a new query and Access tells me that the tables that are involved in the query are not related. Sure enough if I check in the front end, the table relationships are not the same as those in the back end and while the table relationships I need exist in the back end, they do not in the front end.
While the relationships were initially created in the unsplit database, it is possible that I added some of them later during past development/updating processes when the database was already split. This is the only reason I can think of for them to be different.
When I add a relationship in the back end (new table or bug fix) do I also need to add it to the front end if the database is split? if not, why would they be different? What kind of issues can this create?
I am using Access 2007, and I mistakenly created a duplicate table in Relationships. And, I have not been able to removed it or delete it.
View 6 Replies View RelatedI have 3 tables
tblProductInfo
- ProductID
- ProductItemNumber
- JDEDescription
tblFacility
- FacilityID
- FacilityDescription
tblProductFacilityMM
- ProductToFacilityID
- ProductIDFK (combined with FacilityIDFK to make a PK)
- FacilityIDFK
As I'm writing this out, I am realizing that tlbProductFacilityMM.producttoFacilityID is probably not necessary, but that I don't expect that to have much significance to the issue. So I've setup a query between the two tables:
Code:
SELECT tblProductInfo.ProductID, tblProductInfo.ItemNumber, tblProductInfo.JDEDescription, tblProductFacilityMM.FacilityIDFK, tblFacility.FacilityDescription
FROM tblFacility INNER JOIN (tblProductInfo INNER JOIN tblProductFacilityMM ON tblProductInfo.ProductID = tblProductFacilityMM.ProductIDFK) ON tblFacility.FacilityID = tblProductFacilityMM.FacilityIDFK;
And used it to create my subform which is simply a drop down box for tblProductFacilityMM.FacilityIDFK. My main form is one that has already been in use for 6 months or so, it is based off the tblproductinfo table and needs to have the option to select multiple Facilities for each ProductID. I inserted the subform, but when I try to select a facility I get an error that reads:
Quote: Cannot Join Records; Join key of tblProductFacilityMM not in recordset.
I'm trying to create a database at work keep track of projects I'm working on and all the different events that happen during the project.
I want the main table to be customers, which will include the job number (as the primary key) name, address etc. Then I need other tables that have information about the building permit that will include dates city names etc and then another table that would include information on our sales people and so on, there would be maybe 5 tables that all connect back to the customer table.
I have tried this several times and keep running into problems, I'm sure it has something to do with the relationships. I'm missing something. I can create 2 tables and it works fine but once I add a 3rd it wont work.
My db is split into front-end and back-end. In the f-e's Relationships schematic, I can see the relationships as they were defined at the time when the db was split, complete with the one-to-many symbology.
I can add a new table to the b-e and set its relationship as one-to-many, enforcing referential integrity and cascading as I wish - and the schematic (in the b-e) reflects that.
In the f-e, I can then use the <Get External Data - Access Database> function to link to the new table, and I can add the new table to the relationships diagram in the f-e. I can also drag and drop to link primary and foreign keys (within the f-e), but cannot select one-to-many. I'm OK with that, as I understand that the relationship is within the b-e, and this is just a diagrammatic representation.
But I can see the one-to-many relationships between the tables which existed when the db was split, and I would like to be able to see the new table's relationships in a consistent fashion. Updating the linked tables via the Linked Table Manager does not do the trick.
Surely I don't have to split the database again in order to achieve a consistent diagram - do I ?
I am currently using Microsoft Access 2010 32bit, and have one database acting as parent, with a second linked database as a client for people to work with, and the parent database has tables imported from Sage V21 via ODBC. I have used the following code as specified in other examples as follows:
Code:
DoCmd.TransferDatabase acImport, "ODBC Database", "ODBC;DSN=MyDNSMachineName;UID=MyUID;PWD=MyPassword;LANGUAGE=us_english;" & "DATABASE=pubs", acTable, "INVOICE", "INVOICE"
one of the tables has 10k records in it, it only transfers 77 records. After manually attempting an import via the ODBC wizard it finally lets me access all 10k records.I wish to have a single button click delete and import fresh tables without worrying if all the data is coming across.Also, when manually adding a table, I am usually asked by the wizard to specify an index, but with the code above, I am not offered that option and the tables come across with no index. I am led to believe that having tables that link to each other without an index is bad, so how do I ensure an index is created?
Why one would want a unique index on an ID key ? It can't be effectively used in joins and is never used in a where clause. So why have one ?
View 14 Replies View RelatedI am building a database to capture monthly statistics on a number of items. I want to ensure that users don't enter statistics for the same item for the same reporting period. I found the following instruction, but can't make it work:
It suggests that I create multiple primary keys in the table
When I do it, it comes back with an error: Index or primary key cannot contain a null value.
To prevent duplicate records, I use multiple fields indexes, which worked fine until now. I learned that each "empty" fields are consider unique by Access, so not the best in an index to prevent duplicate records. I managed to have it worked using the default value property to give each "empty" records the same value.
Now my problem is that I have a date field which is optional, but I need to use it as a unique identifier in an index. I could again use a default value, but since it has to be a date, I find it confusing. I would rather have a default value of "No date specified" or "-" or even better, "". Unfortunately none of those works with date fields.
How do I create a table that can cross index items in another table. Maybe I am not using the right terms here so let me show a small example.
Say I have a tables of words.
tblWords
numWordID
txtWord
Then I have some entries, all more or less synonyms of each others
fresh
new
clean
Now I want to create a cross-index table, related to the table "tblWords" where I can select synonyms from words already in the table "tblWords", so if I for the word "fresh" add "new" and "clean" as synonyms or entries, if I then go and look at the word "new" it will already have the synonyms "fresh" and "clean", likewise the entry "clean" will then have the synonyms "fresh" and "new".
Kind of a many to many relationship junction table but only with one table!
I hope my explanation have not been to confusing, but let me know if you need a clarification.
Thanks
Hello, I keep getting this error when opening up a database. What can I check to find and fix the problem? TIA
View 3 Replies View RelatedI am pullling data from a query using an unbound form and a query that that uses linked tables. I can not edit the index of the tables, so is there a way i can create a new index for sorting data in a form?
View 2 Replies View RelatedI am creating a table with a make-table query. The only trouble is that I can't figure out how to designate which field will be the primary key. Is there a way to do this...... other than creating the table, then manually going into desing mode and specifying the primary key there? I want this to be automated.
Thanks,
David
I have a linked table to a SQL server table called AllAttendanceEvents.
the AllAttendanceEvents table has index called "AttEvents". I wrote the following code:
set AllAttendanceEvents=currentdb.openrecordset("AllAttendanceEvents")
AllAttendanceEvents.movefirst
AllAttendanceEvents.index="AttEvents"
When it executes the read line statement, it generates the following error:
Operation is not supported for this type of object
Is there any way to get around of this problem with the linked tables?
I have 5 tables and 2 forms. The primary form is what I input all the information into (Tracking) and the other form is to update employee information (update form).
The "Tracking" form is where I add information to 4 of the 5 tables. Here is where I'm stumbling. Would it be more practical to just have 1 table and just expand the fields, or have the form put the information into the separate tables. Those 4 tables are Employee, phone, spotter and radio.
I'm wanting to keep a running tally of who doesn't turn in what equipment on what day.
Using an Access 2003 format database, opening in Access 2007...When I try to open my database I get two errors and it will not open.ID is not an index in this table.ParentId is not an index in this table.
I get the error when it opens with autoexec and when I bypass autoexec. I have a master copy of the database that I tried to link to the first database to import tables but I still get the error.
I have a situation where I have a report which I will generate to print our companies pricebook. I need an index/table of contents for customers to go to the page where a product is to look up prices. The problem is that we add and subtract products on a consistent basis.
So a new product will get added, but of course, to run alphabetically, there's no way to insert it, then renumber the pages for it to be easily found.to use a maketable query, which sorts all of the products alphabetically. Each time it is run, it will delete the previous table. I then need to have an autonumber field created to create my "page numbers". Yes, each time the pricebook is run, products can and will oftentimes get new page numbers.
So my thought is to have a macro run which creates the autonumber field to the table. This will then be the basis for the form, which will in turn utilize the "page number"/autonumber field to both serve as page numbers in the report. And of course, the table which is created each time will be the "table of contents".
I am trying a to build a slot booking database in which users will be able to book slots (ranging from 1-30) on a particular day for a specific site (location).
When trying to build the relationship between slot in tbl_available and slot in tbl_appointment i get the following error "No unique index found for the referenced field of the primary table" the same error pops up when trying to build a relationship between site in tbl_available and site in tbl_appointment.
I need both relationships to be 1 to many.
CompanyID pk (just one company)
CompName
EmployeeID pk
companyID fk
roomID fk
extensionID fk
LName
FName
LocationID pk
RoomNumber (many employees might share same room)
PhoneDirectoryID pk
ExtNumber (employees might share same extension number)
roomID fk
ItemID pk
ItmName (messengers take envelopes to different employees)
equipmentID fk
employeeID fk
EquipmentID PK
eqmtName (equipment might be used many times to deliver jobs)
I just need to know if the relationships for these tables are right.
If you need more information about this, please let me know.
I am converting / developing a database that stores information pertaining to individual birds and their recaptures over many years. Here is a condensed version of the many tables in this database:
tblIndividual Bird:
Autonumber (Primary Key)
Band Number - also, unique to the individual bird
Sex - M or F
etc ..
tblCaptureInformation:
Autonumber (Primary Key)
Band Number - look-up from tblIndividualBird (using hidden Primary Key)
Capture #- # which indicates what capture this is (ex. Intial capture - 1)
Place
Age
Date
etc ...
Each time a bird is captured, we record information pertaining to TIME, MEASUREMENTS, and NEST INFO. So, I have seperated the data based on these headings and made them into individual tables.
Now, my problem .... I have already created a relationship between CaptureInformation and Individual Bird. However, in the last 3 tables I would like to create a drop-down menu which shows the Band Number and Capture Number and make relationships there. What is the easiest way to do this? As of now, when I make a look-up field in the last 3 databases to show this info, the Band Number comes up with the Autonumber (because I am using the CaptureInfo table) which does not really help someone entering the data. Thanks for your help.
Hi,
I am trying to create a db for service orders for customers. At the moment I have four tables, customer, service_order, parts and totals.
I have one form for customer records that has a button that when clicked opens another form for that customer's service orders. The service order form has two subforms, one for parts and one for totals.
When I try to add a new service order for my test customer it says "you cannot add or change a record because a related record is required in the table 'customer'.
As you can see here (http://www.abstractmusic.org/relationships.gif) I have three relationships setup. cust_no in customer table is a PK and so is service_order_no in service_order table.
Also I am having problems with the totals, as the fields are from different tables the equations won't work from within the subform (I guess I need some kind of query). I need the totals in a seperate table other wise I have a total for every part entry.
Any help would MUCH appreciated.
Cheers
Housey
The attached application is what I need to design a form in Access around. Please see if i set up the tables correctly and the relationships. Thanks.
View 1 Replies View Related