Disappearing Changes!

[falkaholic]

I have a system I made that is in use. I day or so ago one of the users went through the inventory database and changed most of the product descriptions.

Later the same day, they went back and the descriptions where back to what they were before!

I've tested doing this myself and it works for me.

No scripts are run turning the changes it so its not that.

I can't see how PEBCAK (problem exists between chair and keyboard) could be to blame.

The only problem is that the system is hosted on FM server and used be more the one user.

anyone else run into this?

[Moon]

My best guess is that the user was in Find mode when making the changes and didn't notice it.

[falkaholic]

Thought of that, but the user was adding/changing the field so it wouldn't make sense since find mode empties the field.

[Vaughan]

Were the values entered into global fields when the data was shared multi-user?

[The Bridge]

I realize that the databases are served by FM Server, but perhaps the user actually opened a different copy of the database with the same name, i.e. a backup of some sort, or a local database, or the proper database via the network (as opposed to the Host button).

Or perhaps someone else restored the system from a prior backup between the times the changes were made and the moment you discovered they disappeared.

Or perhaps someone, faced with updating umpteen product descriptions, is trying to cover his or her butt? Sorry, no disrespect toward your staff intended, but it is always a possibility.

In any case, this is a good example of why it's a good idea to have fields that keep track of record modification date, time, and username. Sorry I can't offer more constructive suggestions.

[falkaholic]

The thing is, they showed me a printed report of al the records, before and after. One had the field all changed, and then one from later on with most of the fields returned. I thought maybe they got them confused but in the database the were back to square one. So i don't think it could be a user coving because there is no way they could have caused it in the first place.

The were no backup restores within days of it (in fact we havn't yet), using retrospect 4 for backups instead of FM server's (the the tech support guys call, not mine) that could be the problem who knows....

[falkaholic]

Nope, no global fields were being used, and even if they were, the fields would at least stay changed for that user, not return to before for all users.

[The Bridge]

In reply to:

---

So i don't think it could be a user coving because there is no way they could have caused it in the first place.

---

Glad to hear it; again, my apologies for any hard feelings my suggestion may have caused.

[falkaholic]

no worries, i think we all know about good old "users"

[Vaughan]

The way globals work, once the user closes the database and reopens them, the global fields return to the "defaults."

[bbaliner]

yeah, I agree with the previous poster on the same database name. It's very possible that there is a copy of that file somewhere, and the user worked on that copy vs the file on the server.

PS Can some one clarify what's meant by "...globals return to defaults..."

Cheers

BB

[BobWeaver]

I had a similar situation with an installation where one user had made his own copy of the files off the server to his laptop, so that when he was out of the office he could refer to the data. He had no intention of altering the data. But, when he was back in the office and even using the opener file to get into the server version, he was still accessing the copy on his own computer. So, opener files won't guarantee that you are getting files off the server. It took quite a while to track down this problem because he didn't always use the same computer. The myterious disappearing/reappearing data problem.

So, check all computers that the user may have used as well as all file servers that may have been connected at the time.

[falkaholic]

I think I figured it out, the user went into the line items database and changed the names there. Since the database is used for other stuff (like price variations and reports) they could easily find themselfs there. The user didn't know the difference from the inventory database. Bad design on my part I guess.

At least thats my leading theory, but seems very likely.