Rob Glaubitz

Okay, I just solved my own problem. That's what happens if the output of the calculation is a number and not text. I changed it to text and now it works fine. Oh well. Hopefully, this will help someone else who did what I did.

I'm having troubles with a related value list with calculations. I used a self-join and a related value list to create a pop-up menu that lists all the names for that particular ID number (the ID is not unique). Works fine if the value list references a text field. However, if the value list references a calculation, then the results get screwy. Sometimes, they show up. Sometimes, they don't. Even odder is that it seems if you start with certain letters, there isn't a problem. For instance, anything starting with "t" seems to work. See the attached file as an example. Note the difference between the two value lists that should be the same. Before you say that value lists don't work for unstored calculations, let me tell you that this IS a stored calculation that references no related files. This seems like a bug to me. However, I might just be doing something wrong. test.zip

I know I can display the fields from db 3 in db 1 via this method but I need to be able to update the third db from the first db. You can't update calculation fields.

I am working on a db with relational files two levels deep, ie. the first db relates to second db which then relates to a third db. Fields from the second db are displayed in the layout for db 1 within a portal. I would like to be able to update fields in the third db from the interface in the first db. However, the key between dbs 1 & 2 is different than the key between dbs 2 & 3. I can figure out how to display the fields from db 3 in db 1 (using calc fields in db 2 and then adding those calc fields to the portal) but I can't update them. I tried to find a way to get the key between db 2 & db 3 to db 1 (using calc fields) so I could create a relation from db 1 to db 3 but, because of the portal, the calculation field in db 1 only displays the key for the first record in db 2 no matter what the active portal row is. Any ideas? Hopefully, I explained it clearly enough that you can figure out what I'm trying to do...