June 4, 200223 yr I have a calculated field in DB A that I am using as a value list in DB B. The DB B field is set up as a pop up field. When I go to the field to select a value the list pops up fine with the appropriate values BUT as soon as I select the value I want I get a dialog box telling me I can't modify the field. I vaguely recall that there is a need to put another field in one of the databases that acts as an "intermediary" or some such thing. TIA for any feedback.
June 4, 200223 yr Sounds to me like you have actually got the calculated field on the layout, with a popup list of teh same field. (Or possibly just another calculated field) As the field is "calculated" then you can't modify the content of the field. To prove this you can go into Find mode - then you can use the popup list. Your approach using the related calculated field is fine, you're just applying it to the wrong field.
June 4, 200223 yr Author Mark, Thanks for your quick reply. Here is a little more on the db structure: A field called Full Name is calulated by concatenating First Name, Middle Initial and Last Name. This field resides in a database called Contacts. In a second database (not just a different layout) called Credit Reports I created a portal (referring to the Contacts DB) and placed the field Full Name::Contacts in it. I made the field a pop up and clicking on it in the Browse mode shows the correct list of contact - I just can't select one due to the "You can't modify this field" dialog. Is there a possibility the problem lies with the DB relationship links? I actually have a 3rd DB called Companies linked to Contacts and Credit Reports. Each of the three files has a field called Company ID which is a unique number for each record in the Companies DB. This way I can enter the Company ID in my Credit Report DB and it will bring up the associated company name. It also means that the pop up field under question is populated with only those contacts associated with the given company rather than all the contacts in the Contacts DB. It works just like I wanted re the population of the value list - if I can just get around the "you can't modify this field" message. Any additional commenst will be appreciated.
June 4, 200223 yr As Mark suggests, you are getting the error because you are trying to edit a calculated field, in this case Full Name. The solution to this is to apply the Full Name value list to a standard text field.
June 4, 200223 yr Author Thanks Bridge and Mark - it now works. I had misread Mark's post but now I understand and the field works exactly as I wanted. Again, thanks.
Create an account or sign in to comment