mleiser Posted October 14, 2021 Posted October 14, 2021 I added two container fields in my database. I put a picture in each and set it as global. Worked fine. Went to a second computer and opened the file and they're not there. Closed my file and reopened it and they're not there. I put them in originally with copy paste. Any idea what I'm missing? Thanks.
comment Posted October 14, 2021 Posted October 14, 2021 That is the expected behavior of global fields in a hosted solution. At the beginning of each session, global fields are initialized to the values they held the last time the file was opened locally. Any changes to these values last only for the duration of the session and are limited in scope to the user that makes them. https://help.claris.com/en/pro-help/content/global-fields.html?Highlight=global session
mleiser Posted October 14, 2021 Author Posted October 14, 2021 Thanks If that's the case, if I want to put a picture into every record in a file (same picture, like maby a logo), how would I go about doing it without losing it when I close the file on my network?
comment Posted October 14, 2021 Posted October 14, 2021 I believe the most common method is to keep a one-record Preferences table with 2 fields (or rather 2 sets of fields): a regular field and a global one. Then have your startup script populate the global fields with their regular counterparts. Alternatively, you could open the file locally, populate the global field, then host it again. But you would have to do this every time you want to change the logo (or any other preference).
mleiser Posted October 14, 2021 Author Posted October 14, 2021 Can I do something like this. Put the picture in every record, not globally. That I know how to do. But how would I get it into a new record automatically like you can do with regular data? This is a container field. Thanks
comment Posted October 14, 2021 Posted October 14, 2021 49 minutes ago, mleiser said: Put the picture in every record, not globally I don't think you would want to do that. It goes against the very core principle of a relational database that each fact is stored in one place only.
Recommended Posts
This topic is 1398 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now