Records disappear after being used in IWP

[Lambert]

Hi, has anyone any experience regarding this problem?

Records disappear after being used in IWP.

There are no "delete records" functions available for the users, no "button" or "command options", and no "account privileges" to delete records, so it is not possible for them to delete any records in any way.

However, records keep disappearing without a trace now and then, and only when used in IWP.

The database contains approx. 1000 records, in 1 master file, and is presented with IWP to approx.100 users in 5 related files.

[IdealData]

Thoughts...

1. Upgrade FMSA to latest.

2. Are related records getting their key fields re-written, thereby appearing to "lose" records.

3. Are records actually disappearing, i.e. the record count is reduced.

[tgilders]

If the users don't have any reason to delete you can remove that privilege from the privilege set that is being used for the IWP access. Keep in mind that if a script is set to Full Access and doing any deleting of records in the same file, then the privilege set access is trumped by the full access script.

Lastly, are they possibly deleting data in a related table, which deletes data in another related table through a relationship configured to delete related records?

[Lambert]

Thank you for your answers.

There are no deletion functions of any kind to delete records, available to the users.

No scripts present in any file to do so. The key field is only editable in the “master file”.

The records are created and deleted in the “master file” via the key field.

If the record is deleted in one of the 5 sub files, it will still be present in the other files, including the master file. Only when deleted in the master file, by the administrator, it will be deleted in all files. When a record is created it gets an automatically created id number in an id field (creation number) in each of the 5 related sub files. The users have no access at all to the id field. If the content of the key field would be damaged in one of the sub files, the record is still traceable in that file, via the id field. The records only disappear in the one sub file where they have being used with IWP.

[tgilders]

I know you've indicated that IWP users have 'no way' to delete records, but the only other thing I can think of right now is to ask if the Status Bar is hidden and locked for IWP Users. If it's just hidden, a user can click to open it and potentially have access to a delete command.

I just tested a file, and if the user doesn't have delete capability via access privileges, it 'grays out' the delete icon on the status bar.

Perhaps check the web-publishing server logs to see if there is anything peculiar going on there as well.

[Lambert]

Status bar hidden and locked.

I have not worked with server related problems at all, but the guy ho does that usually, is occupied with other tasks for the moment. I find the information in the logs hard to understand with my level of experience in reading logs, (none).

Do you have any suggestions where I can find instructions on how to interpret the information in the logs.

Thanks!

[legal2justice]

I found that in a list view in IWP that as the user selects a record, when they return to the list, they do so on the next record. You may want to add a script step that returns the user to the first record.

If you show the status area you will see more clearly what I am referring to. All of the records remain, however only the ones proceeding the viewed record remain visible. If you change records in the status area they all come back.

Hope this helps.

[Lambert]

The records get deleted, even thou there is no deletion function available, they disappear “physically” from the database when edited in IWP and must be restored from a backup file.

[Vaughan]

Back in the golden age of IWP -- FMP 4.0 using CDML -- there was a neat little trick whereby the IWP account needed to have delete privileges so that the web publishing engine could remove records that failed the field-level validation. What seemed to happen was the web engine would add new records, then check for validation errors, and delete the record if it failed.

For your problem, perhaps the web engine is deleting records that fail validation. Check whether there is field level validation set up for the records; if so, perform a test whereby you edit an existing record to deliberately fail validation. See what happens.

The only other issue is to check whether any relationships allow cascading deletes.

[Lambert]

No validation on any fields, no cascading deletion possible.

[Nichole]

Hi, has anyone any experience regarding this problem?

Records disappear after being used in IWP.

There are no "delete records" functions available for the users, no "button" or "command options", and no "account privileges" to delete records, so it is not possible for them to delete any records in any way.

However, records keep disappearing without a trace now and then, and only when used in IWP.

The database contains approx. 1000 records, in 1 master file, and is presented with IWP to approx.100 users in 5 related files.

i have this same error. I'm using 8.5 to edit but it's going on an 8 v4 server. i ended up putting a refresh button on it to go back to the first record. But it is still irritation that it would just file through the records. I've tured it into a basic view only they can't do anything but view and some how be able to click on the different records. if there is a fix or a way to get around i would like to know. Thanks