Just a couple guesses because I haven't tried this...
Did you try "Guest" and "[Guest]"?
Did you run the script with Full Access privileges?
Yes and yes. I even went back and double-checked. Used both "Guest" and "[Guest]", gave the script full access. No luck
Rather than the built-in [Guest] account, it might be worth installing your own default account instead. Just a thought.
That might do it - but I want the user to be able to download this, login with the [Guest] account so they don't have to put in a password. If I don't find a better way, I guess I can create a no-password account and call it "Guest2" or something like that. Then I can deactivate the [Guest] account, and do the same stuff as before only this time deactivate the "Guest2" account.
Doesn't seem very elegant.
It’s no less “elegant” than doing something that doesn’t work.
But yes, that’s what I mean. In 25+ years of working with FileMaker, I’ve learned that sometimes, you just work around one of the product’s limitations (every product has some) and keep going. Not worth the emotional investment of wondering why it doesn’t work the way you think it should.
Might be worth a Product Idea. Since disabling the account on all databases is considered a security best practice, I don’t know if it’ll go anywhere. Still, if you consider it a fight worth taking up, have at it!
I've bumped into this too. The [Guest] account is an exception but I do not see why we cannot enable/disable it using the script. You'll have to create and work with your own accounts.