Multiple Primary Key possible?
139090
If you refer to databases, no, it's not possible.\nA table can have a single primary key, which are used to uniquely identify a record. Aside from that a table may have a number of keys and foreign keys.
518312
No. It is fairly easy to do if you are familiar with database design; your biggest challenges will be in how you store and order your information, not in how it will be displayed.
560387
Hello\nThere is some software that you can use , but I recommend ORACLE software they have a great database software with a great tutorial. \ngood luck there wonderful.
184667
just create them either in Yahoo, MSN etc.\nNot sure how many they allow, I know friends that have at least 6 different IDs.
501286
Not completely sure I follow the question.  But if you are trying to store parameters, repeating units, etc.. I would recommend a generic "code" table that can house multiple types of values.  You could have a table with a Type, subtype, values and description that could hold all kinds of values.  \n\nType: Construction\nSubType: tool\nValue: hammer\nDesc: tool to pound on things\n\nnext record\nType: Construction\nSubType: measurement\nValue: inches\nDesc: english measurement\n\nnext record\nType: Construction\nSubType: measurement\nValue: centimeters\nDesc: metric measurement\n\nnext record\nType: Query\nSubType: Parameter\nValue: RunDate\nDesc: Time surrounding query execution\n\n\nAnd so on and so on.....\n\nselect * from code_table where Type = 'Construction'\nand SubType = 'measurement'\n\nIt is easy to replicate, extend and edit.\n\nGood Luck in pursuing your answers.
948329
It sounds like you are using a linked table that does not have a primary key. Without a primary key, I think Access looses track of which row is which, and gets this error. Even if you don't want to use a primary key, you could add a primary key column to the backend table (for example, with an auto-increment value) just for Access to use. Then you can leave that column out of your queries in Access.
142385
Normalization is when you make a database not have redundant information. Technically, if you have a table of people and addresses, each state should be in a different table with a foreign key referring to it in the people table. For example:\n\nPeople\n-----------\npid - primary key int(10)\nname\naddress\ncity\nstateid - foreign key int(2)\nzip\n\nstates\n--------\nstateid - primary key int(2)\nstateabbrev\nstatelongname\n\nIn that way no single piece of data should be in the database more than once. But that's fifth normalization which might not make sense for what you're doing.
292739
Yes, you can and it's not even that hard!\n\nOracle is a highly scalable and secure relational database system used to maintain business information.
692712
The best way to do this is to create a query that concatinates the two fields (assuming that the title of the column and the data in each row is the same). To do this you need to created a new Primary Key on your output table which contains both the columns from the two different tables (this is known as a compound key).\n\nHope this helps.
967929
Best way is to have 2 tables.  A header and details table.\n\nThe header table will have one row per sale.  Key field would be invoice number.\n\nThe detail table will have details of each sale.  One row per item.  Key field would be invoice number and item number\n\nJoin field would be invoice number.
426826
This is tricky.  You really need a new field that will tie the correct entry and exit records together.  The only way I can see it is to add a new numeric field (call it entry_exit_id or something).  Then you'd need some code that sorts your data by persons name, entry time.  Then it would loop through each record and assign a unique counter number to each entry/exit pair that goes together.\n\nAfter that - you'd be able to use Group By to group on the name and entry_exit_id. Then you could do the math.
691193
Hi .. \n\ni guess the following page can reslove your issue\nhttp://www.phpfreaks.com/postgresqlmanual/
537043
You take the primary key from the two tables that you are trying to relate, and copy them into your relationship table.
350481
If you want to keeps your costs low.  Then you'll probably be using PHP and MySQL, or possibly Postgres.  The last two are the database programs to store your data.
618620
primary key .. is the key that's u cant have duplicated value from it for the single table\n\nforeign key is the primary key for relation table between two tables .. refers for the primary key of another one \n\nor just refer to primary key for another table \n\nfor more information\n\nvisit\n\nhttp://en.wikipedia.org/wiki/Foreign_key
3707
The PRIMARY key is the FIRST or PREFERRED key to use in retrieving data from the table.  It should (usually) contain UNIQUE information for the record that you are looking for.  The SECONDARY key is an ALTERNATE choice of data access which usually retrieves more data (records) because the key is GENERIC to the table.
409434
1. As a matter of fact, you should first see what is the exact relationship between tables. Maybe in some of them you need to create FK(foreign keys).You should create PK for every table but check first the things I've writhed earlier. Anyway, a table cannot contain 2 PK at the same time... so, I think you already have at least one tables who contains ENO and RPT_NAME at the same time... be careful. \n2. you can use a Stored Procedure to update your tables (not recommended).