I'm in between a rock and a hard place on this one...
I'm building an ADP project w/SQL server back end. I have a main form with several subforms. I would like to have the data in my subforms sorted in a certain order, but the field I want to sort on is a field that is joined with a lookup...
Problem solved!
I took the suggestion of cmmrfrds and created a unique index (composite of 2 columns), and added a unique primary key column. This helped in solving the problem. But the root of my getting the error message is because of the trigger I was executing on the Update of the table...
How then do you enforce uniqueness (at the database end) of the employee/charge number combination without making them a primary key? I'm using SQL 2k.
Sort of. I'm updating the related table where it is a foreign key in the relationship. But this column, along with another column in this table, in combination, form the primary key of the table (it is a classic model of a many-to-many relationship). Let me see if I can illustrate an...
I have an ADP project in Access 2003 with SQL 2k back end. I'm trying to update a record thru a form, in which the recordsource happens to be a table with a 2-field primary key. Both of the PK fields are also foreign keys to other tables. I can add new records using the form just fine, but...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.