Global field not retaining changes - please help

[hlabonte]

I have a database with several tables. One table, contains several global fields which are referenced from other tables. In my 'global' table, there is only one record. I have one field mid_locked which is a calculation based on a few other fields in that table. That value can change when the user sets other fields (dates, periods, etc).

I reference my global field mid_locked in my main data table. The problem is, the field does not retain any value changes because it is defined as a global. I can get the value changes to stick if I check "do not store results", but then I can not reference the field from my other table as it's not related.

Any thoughts on how to make this solution work?

Thanks in advance.

[crpatter]

Two thoughts...

First,

if the sole purpose of the table is to store global values, the fields shouldn't need to be defined a global. You may want to change the fields from being global if you will never create more than one record in your globals table.

Second,

you can define a relationship between your "global" table and any other table that using a Cartesian join(the 'x' relationship operator). A cartesian join connects all records from one table to all records of another table no matter what the values of the join fields are. This allows you to obtain the values of global fields from other tables. Very handy.

Hope this helps

[Søren Dyhr]

One table, contains several global fields which are referenced from other tables. In my 'global' table, there is only one record.

'

This seems like overkill, if the table is considered global, will there be no need to have the fields in it global as well. When I make such things, do I usually pull data over a relation where the global side of the realions key is an autoenter setting the keyfield to Get(Username) ...this makes that particular record linkable from an unstored calc'field (...guess with what??) from all the other tables subscriping to the values behaving global'ish.

The reason for storing in ordinary field is to retain the values saved, between sessions.

--sd

[hlabonte]

Thank you so much for the speedy responses. The cartesian join is just what I needed! Thank you, thank you, thank you!