Script "hiccups" in IWP

[smkanagawa]

Hi!

I'm using IWP to run a relatively simple registration database on the web. Link to it is here (the database is live, but the opening page is still telling people to come back later to register)

GEAR UP showcase registration

Everything seems to be working well, and I wanted to open it up to the public next week, but I just got an email saying that a user was able to "see" another person's registration after hitting "Click Here to Register" (which usually produces a blank record and switches to the first layout) -- I couldn't figure out how this happened except maybe that the script "hiccuped" and skiped the "create new record" step.

Has anyone heard of this tendency for IWP scripts to skip steps? Is it common enough that I should be worried? All my other testers haven't had a problem. Is there a way for me to design the permissions so that this doesn't happen again?

[Reed]

One way to avoid users seeing other records is to build a layout with all globals to do the data entry and then have the script use the global values to create the new record.

I've observed one (intermittent) case where a script step is skipped, but not with IWP. It involved a relogin script that switches back out of kiosk mode after being in kiosk mode. But the problem only happens after the DB has been open in kiosk mode for at least a couple of days.

Also, it's probably a good idea not to have guest login available to connect via FMP. I was able to connect to your DB with FMP and in that case I was able to see all your layouts, and all the registration records.

[smkanagawa]

Thank you so much for the advice. I'll work in those changes. This is all still very new to me. I really appreciate the help!!