jkarol

Thanks so much for the quick help!

I have the simplest loop script that isn't working and I'm tearing my hair out trying to fix it. It goes like this: Loop If ["Field = "no""] Omit Record End If Go to Record/Request/Page [Exit after last, Next] End Loop It's part of a larger script, but for testing, I made it into a script of its own and it still doesn't work. I have 317 records, and in 158, that field is equal to "no". But when I start with all records shown and run that script, it consistantly leaves me with 234 records. Could someone please give me an idea of what I could be missing? I'm used to having to hunt down the little things, but this is ridiculous... Thanks.

I really don't see how this applies to my situation. I have a file with many records that is used by many users. I want any of these users with permission to be able to change a date field that applies to all records. I don't want it automatically calculated; I want those users to be able to change it to whatever they want whenever they want. That's why I wanted the date to be stored in a global field that user's could change--but I understand now that this is not how filemaker works. So I don't see how creating a login file would be the answer to my problem (besides being a lot less elegant than the way I was hoping it would work.) Really I posted to this forum hoping to get some ideas about how to solve my problem not to be lectured on all the unrelated benefits of one way of designing fm databases. I like fm but would like to see added features. I am not the first person to post to this forum thinking that being able to change a global field in a multi-user environment would be beneficial. If there is already a way around this, that doesn't mean that the simple way wouldn't be an improvement. In short, I am not "blaming my tools", I am asking for help in how to use them to accomplish what I am trying to accomplish. As yet, I have not received an answer.

So it isn't broken, it's just designed in such a way that I have to create a separate file for my users to use just to change a single global field that relates to all the records in the original file. And it isn't broken because it would be bad if users could change a loop counter. Well there's no reason that users couldn't edit global fields in a multi-user environment while still keeping other fields protected. I understand that there are ways to accomplish what I want to accomplish, but just not as elegant a way as I feel there ought to be. So I guess broken means not working in the way it was designed to work--even if it was designed to work in an inflexible way.

I have the same problem. I have one database with around 200 records with an overall "Effective as of" date field that should apply to all of them. I have the Effective Date as a global field displayed on all the records, but I can't change it while sharing it. Seems silly to have to have a separate database just to hold a single date. In another database I have a different global field for each state. I guess I could put them all in a separate database with each state a different record, but I was hoping to leave them where they are so that a change in one state applies to all records. Any ideas? This seems to be a not uncommon issue, anyone know if changing global fields in shared databases is allowed in 6.0?