Thanks for your reply Jack. And so close too. I work up at the Veterans Home here in Yountville. I assist resident's in resolving grievances with the Home. I created this database a few years ago with little knowledge and less forethought. I was forced to improve upon it a few months ago in order to link it to Pendragon Forms on my Palm. In doing so, I changed the primary key to the person's name so that the name, not the autonumber, would be displayed on the palm.
The database consists of several tables ranging from Departments, staff info, ombudsman codes, resident table, and a grievance table. The grievance table is linked to Pendragon Forms on my palm as well as a query linked to a form within the database to track unresolved grievances. I use the datasheet view on the resident table to enter new grievances at my pc because I've found it more time efficient to move from one record to the next.
My problem, or at least the problem I'm currently working on, is that when i changed the primary key to the resident's name and deleted the manufactured primary key, I screwed up the link to the records in the grievance table. Now when I click on the + sign in datasheet view in the resident table to view all of the grievance records for that resident, I am promted for a parameter value. If I copy and paste the PK value for that resident record, the grievance records associated with that resident record are viewable in the subdata sheet. If I don't put in a value when promted for the parameter value and press enter, the subdata sheet appears empty.
What changes do I need to make in order avoid the promt for the parameter value?
