-find leaves FM file in find mode...?

[ibiubu]

http://xxx.xxx.xxx/FMPro?-db=Research.fp...dback&-find

When this URL is executed, the browser goes to the -format page which contains info from a related record. If I take a look at my main FM file (research.fp5) it seems to still be in find mode. Should it not return to browse mode once the -find in the above URL is completed?

LR

[Steve T.]

Hi, Larry! Hmm... In a sequential db, I have never seen FM left in FIND MODE... in fact, I did not even know it "physically" entered find mode... I would just see a blink and see the result set and had assumed it was executed in the background. Even with a related record, though, doesn't it just show information in a portal? I mean, we don't actually search the other db, right? I dunno... I could be wrong. Anyway, I think you're right to question being in FIND mode... it should execute and succeed or execute and fail but should not be left waiting for user input or additional actions.

Just my 2 sense...

--ST

[Garry Claridge]

I've seen this happen before. However, I've been straining my brain to to remember what was causing it.

I'll keep straining!!! Good Luck.

Garry

[ibiubu]

Thanks for the replys. I was able to FINALLY find the problem. Here is what was causing it:

I started cleaning EVERYTHING out of my file. I deleted all relationships, then all scripts, then all value lists, then all but one layout, then all but one field. I tried creating a blank clone of the file, and even tried recover.

And it would still get stuck in find mode whenever a -find was submitted from the web.

FINALLY I went into my access privileges and started deleting passwords. And bingo, it started working correctly. Now when a -find is performed from the web, the file does not get stuck in find mode.

After deleting the password, I was able to again just re-create it without a problem. The two things seem completely unrelated, so go figure. Moral of the story, if you have a FM file acting strangely, don't forget to check to see if one of your passwords is the cause of the problems.

LR