While i am posting...

I sometimes find that my FMPU (5.5v3, running on W2K) ceases to allow me to delete records or fields. Everything else remains completely functional, except for the delete commands, which do nothing.

Problem is fixed upon restarting the program, but then just appears (apparently) randomly again.

Any clues?

Have you applied any field level privileges which prevent certain functions when the field level criteria are met ?

nope - nothing like that...

"I sometimes find that my FMPU (5.5v3, ..."

I believe I recently read that for 5.5 the latest updater is v4. You might check the FMI site.

"...ceases to allow me to delete records or fields."

To "delete" data from a field you should be using -edit, I believe.

I never had this problem with fields. But my FMU lock the records and the records cannot be deleted. Restarting usually unlock them, bus as you wrote, it is again back to lock stage.

Did you try to delete records from remote copy of FM?

Whoops - i meant 5.0v3 with web companion v6 (sorry about that!).

Keith: the problem is within FMP, NOT through the web interface.

Anatoli: Haven't tried a remote copy. I presume you haven't been able to cure your problem?

joel

I just tried to connect to our Unlimited machine and delete the record, which was locked for web deletion and it works. No problem

I have faced with that problem many times. As you told, It becoms okey after I restart the program. I can not delete the records and the fields on file maker (but only it occurs after I start using the databases over web pages) but if I dont want to close my databases I try to delete the records by using web pages and it works... Why ? Still I wonder the answer...

the answer ...

may well be to not allow the client to delete. When that permission is allowed, it may be possible for a disgruntled, but knowledgeable user to delete up to all of your valuable records.

FWIW, it is possible to not allow the delete permission, but to perform the delete using a ScriptMaker script which, if allowed, performs the event behind Web Security and without regard to the other Web Security permissions.

Of course, the usual cautions to running a single-threaded ScriptMaker script will then apply.